Methods, systems, and computer program products for modifying bandwidth and/or quality of service in a core network

ABSTRACT

Bandwidth and/or Quality of Service (QoS) may be modified in a Regional/Access Network (RAN) that includes a core network, the RAN facilitating differentiated end-to-end data transport between an enterprise, a Network Service Provider (NSP), and/or an Application Service Provider (ASP) and a customer Premises Network (CPN). Application Programming Interface (API) calls are used at the enterprise, NSP, and/or the ASP to communicate with the RAN to query a resource allocation in the core network that is assigned to the enterprise, NSP, and/or the ASP. API calls are also used at the enterprise, NSP, and/or the ASP to communicate with the RAN to modify the bandwidth and/or the QoS of the resource allocation in the core network that is assigned to the enterprise, NSP, and/or the ASP.

FIELD OF THE INVENTION

The present invention relates to communication networks, and, moreparticularly, to managing bandwidth and/or Quality of Service (QoS) incommunication networks.

BACKGROUND OF THE INVENTION

The Internet is a decentralized network of computers that cancommunicate with one another via the Internet protocol (IP). Althoughthe Internet has its origins in a network created by the AdvancedResearch Project Agency (ARPA) in the 1960's, it has only recentlybecome a worldwide communication medium. To a large extent, theexplosive growth in use and traffic over the Internet is due to thedevelopment in the early 1990's of the worldwide Web (WWW), which is oneof several service facilities provided on the Internet. Other facilitiesinclude a variety of communication services such as electronic mail,telnet, Usenet newsgroups, internet relay chat (IRC), a variety ofinformation search services such as WAIS and Archie, and a variety ofinformation retrieval services such as FTP (file transfer protocol) andGopher.

The WWW is a client-server based facility that includes a number ofservers (computers connected to the Internet) on which Web pages orfiles reside, as well as clients (Web browsers), which interface theusers with the Web pages. Specifically, Web browsers and softwareapplications send a request over the WWW to a server requesting a Webpage identified by a Uniform Resource Locator (URL) which notes both theserver where the Web page resides and the file or files on that serverwhich make up the Web page. The server then sends a copy of therequested file(s) to the Web browser, which in turn displays the Webpage to the user.

The topology of the WWW can be described as a network of networks, withproviders of network service called Network Service Providers, or NSPs.Servers that provide application-layer services as previously describedmay be described as Application Service Providers (ASPs). Sometimes asingle service provider does both functions within a single business

In recent years, broadband access technologies, such as digitalsubscriber line (DSL), cable modems, asynchronous transfer mode (ATM),and frame relay have facilitated the communication of voice, video, anddata over the Internet and other public and private networks. Becausebroadband technologies are typically deployed by a single transportservice provider, like a Regional Bell Operating Company (RBOC), theirRegional and Access Networks (RAN) are often shared by many NSPs andASPs offering services that range from Internet access and VPN access toVoice over IP, Video on Demand, and Gaming. Up until recently, a givenCustomer Premises Network (CPN) would have been connected to a singleservice provider in a generic way, however a new standard for RANservice (DSL Forum TR-059) provides a RAN architecture that allowssimultaneous access to multiple NSPs and ASPs and for differentiatingthe data transport service provided by a RAN to these service providers.

Moreover, broadband access technology has allowed service providers toexpand their content and service offerings to both business and homeusers. For example, a user may subscribe to multiple services orapplications, such as voice service, Internet access service, a videoservice, a gaming service, etc. from one or more service providers.These services and/or applications may be delivered over a singlenetwork connection, such as a DSL line. Unfortunately, with multiple newconnectivity options and applications that require specificcharacteristics from the network, there is also a need to establish QoSand bandwidth allocation among multiple services and/or applications soas to customize the content delivery according to the users' and/orproviders' preferences.

SUMMARY OF THE INVENTION

According to some embodiments of the present invention, bandwidth and/orQuality of Service (QoS) may be modified in a Regional/Access Network(RAN) that comprises a core network, the RAN facilitating differentiatedend-to-end data transport between an enterprise, a Network ServiceProvider (NSP), and/or an Application Service Provider (ASP) and acustomer Premises Network (CPN). Application Programming Interface (API)calls are used at the enterprise, NSP, and/or the ASP to communicatewith the RAN to query a resource allocation in the core network that isassigned to the enterprise, NSP, and/or the ASP. API calls are also usedat the enterprise, NSP, and/or the ASP to communicate with the RAN tomodify the bandwidth and/or the QoS of the resource allocation in thecore network that is assigned to the enterprise, NSP, and/or the ASP.

In other embodiments of the present invention, the core network isqueried directly from the RAN to obtain the resource allocation in thecore network that is assigned to the enterprise, NSP, and/or the ASP.

In still other embodiments of the present invention, an OperationalSupport System (OSS) associated with the core network is queried toobtain the resource allocation in the core network that is assigned tothe enterprise, NSP, and/or the ASP.

In still other embodiments of the present invention, the bandwidthand/or the QoS of the resource allocation in the core network that isassigned to the enterprise, NSP, and/or the ASP is modified directlyfrom the RAN.

In still other embodiments of the present invention, the RANcommunicates with an Operational Support System (OSS) to modify thebandwidth and/or the QoS of the resource allocation in the core networkthat is assigned to the enterprise, NSP, and/or the ASP.

In still other embodiments of the present invention, the QoS of theresource allocation in the core network that is assigned to theenterprise, NSP, and/or the ASP is traffic priority.

In further embodiments of the present invention, a query networkresource request message is sent from the enterprise, NSP, and/or theASP to the RAN that contains a request for information on resourceallocation in the core network that is assigned to the enterprise, NSP,and/or the ASP. A query network resource response message is sent fromthe RAN to the enterprise, NSP, and/or the ASP that contains theinformation on resource allocation in the core network that is assignedto the enterprise, NSP, and/or the ASP.

In still further embodiments of the present invention, a change networkresource request message is sent from the enterprise, NSP, and/or theASP to the RAN that contains a request for changing the bandwidth and/ortraffic priority of the resource allocation in the core network that isassigned to the enterprise, NSP, and/or the ASP. A change networkresource response message is sent from the RAN to the enterprise, NSP,and/or the ASP that contains an acknowledgement for the change networkresource request message.

In still further embodiments of the present invention, the enterprise,NSP, and/or the ASP is authenticated with the RAN prior to using APIcalls at the enterprise, NSP, and/or the ASP to communicate with the RANto query the resource allocation and prior to using API calls at theenterprise, NSP, and/or the ASP to communicate with the RAN to modifythe bandwidth and/or the QoS of the resource allocation.

In still further embodiments of the present invention, an establishservice session request message is sent from the enterprise, NSP, and/orthe ASP to the RAN that contains an identification of the enterprise,NSP, and/or the ASP and authorization credentials. An establish servicesession response message is sent from the RAN to the enterprise, NSP,and/or the ASP that contains an authentication result.

In still further embodiments, the RAN is coupled to at least one edgenetwork. Moreover, API calls are used at the enterprise, NSP, and/or theASP to communicate with the RAN to modify the bandwidth and/or the QoSof the resource allocation in the core network and the at least one edgenetwork that is assigned to the enterprise, NSP, and/or the ASP.

In still further embodiments, the RAN is coupled to a plurality of edgenetworks of different types. Moreover, API calls are used at theenterprise, NSP, and/or the ASP to communicate with the RAN to modifythe bandwidth and/or the QoS of the resource allocation in the corenetwork and the plurality of edge networks that is assigned to theenterprise, NSP, and/or the ASP.

Other systems, methods, and/or computer program products according toembodiments will be or become apparent to one with skill in the art uponreview of the following drawings and detailed description. It isintended that all such additional systems, methods, and/or computerprogram products be included within this description, be within thescope of the present invention, and be protected by the accompanyingclaims.

BRIEF DESCRIPTION OF THE DRAWINGS

Other features of the present invention will be more readily understoodfrom the following detailed description of specific embodiments thereofwhen read in conjunction with the accompanying drawings, in which:

FIG. 1 is a block diagram that illustrates a conventional digitalsubscriber line (DSL) network;

FIG. 2 is a block diagram that illustrates communication between endusers and an application service provider (ASP) and a network serviceprovider (NSP) via a regional/access network;

FIG. 3 is a block diagram that illustrates the regional/access network;

FIG. 4 is a block diagram that illustrates a broadband remote accessserver (BRAS) and a routing gateway (RG) in a network;

FIG. 5 is a block diagram that illustrates access session types in thenetwork of FIG. 4 in accordance with some embodiments of the presentinvention;

FIG. 6 is a block diagram that illustrates traffic classification andqueuing treatments in accordance with some embodiments of the presentinvention;

FIG. 7 illustrates business model options for using bandwidth on acommunication medium in accordance with some embodiments of the presentinvention;

FIG. 8 is a block diagram that illustrates relationships between asubscriber, the RG, the regional/access network, an ASP, and an NSP;

FIGS. 9-12 are block diagrams that illustrates a data architecture(model) for managing quality of service (QoS) in a network in accordancewith some embodiments of the present invention;

FIG. 13 is a block diagram that illustrates an application frameworkinfrastructure for managing QoS in a network in accordance with someembodiments of the present invention;

FIG. 14 illustrates a messaging flow for a service providerauthentication scenario using the application framework infrastructureof FIG. 13 in accordance with some embodiments of the present invention;

FIG. 15 illustrates a messaging flow for an application level bandwidthand QoS query scenario using the application framework infrastructure ofFIG. 13 in accordance with some embodiments of the present invention;

FIG. 16 illustrates a messaging flow for an application level bandwidthand QoS modification scenario using the application frameworkinfrastructure of FIG. 13 in accordance with some embodiments of thepresent invention;

FIG. 17 illustrates a messaging flow for an application flow controlrecord creation scenario using the application framework infrastructureof FIG. 13 in accordance with some embodiments of the present invention;

FIG. 18 illustrates a messaging flow for an application flow controlrecord deletion scenario using the application framework infrastructureof FIG. 13 in accordance with some embodiments of the present invention;

FIG. 19 illustrates a messaging flow for a NSP Point-to-Point Protocol(PPP) session level bandwidth and QoS modification scenario using theapplication framework infrastructure of FIG. 13 in accordance with someembodiments of the present invention;

FIG. 20 illustrates a messaging flow for a ASP/NSP PPP session levelbandwidth and QoS query scenario using the application frameworkinfrastructure of FIG. 13 in accordance with some embodiments of thepresent invention;

FIG. 21 is a block diagram that illustrates a turbo button architectureusing the application framework infrastructure of FIG. 13 in accordancewith some embodiments of the present invention;

FIG. 22 is an event diagram that illustrates operations of the turbobutton architecture of FIG. 21 in accordance with some embodiments ofthe present invention;

FIG. 23 is a block diagram that illustrates a video conferencingarchitecture using the application framework infrastructure of FIG. 13in accordance with some embodiments of the present invention;

FIGS. 24 and 25 are event diagrams that illustrate operations of thevideo conferencing architecture of FIG. 23 in accordance with someembodiments of the present invention;

FIG. 26 is a block diagram that illustrates traffic classification andqueuing treatments for the video conferencing service in accordance withsome embodiments of the present invention;

FIG. 27 is a block diagram that illustrates operations of a videoconferencing architecture in accordance with some embodiments of thepresent invention;

FIG. 28 is a diagram that illustrates network topologies for supportinggaming applications in accordance with some embodiments of the presentinvention;

FIG. 29 is a block diagram that illustrates a gaming architecture usingthe application framework infrastructure of FIG. 13 in accordance withsome embodiments of the present invention;

FIG. 30 is a block diagram that illustrates traffic classification andqueuing treatments for the gaming service in accordance with someembodiments of the present invention;

FIG. 31 is an event diagram that illustrates operations of the gamingarchitecture of FIG. 29 in accordance with some embodiments of thepresent invention;

FIG. 32 is a framework infrastructure for managing bandwidth and/or QoSin a core network in accordance with some embodiments of the presentinvention; and

FIG. 33 is a flowchart that illustrates operations for modifyingbandwidth and/or QoS in a core network in accordance with someembodiments of the present invention.

DETAILED DESCRIPTION OF EMBODIMENTS

While the invention is susceptible to various modifications andalternative forms, specific embodiments thereof are shown by way ofexample in the drawings and will herein be described in detail. Itshould be understood, however, that there is no intent to limit theinvention to the particular forms disclosed, but on the contrary, theinvention is to cover all modifications, equivalents, and alternativesfalling within the spirit and scope of the invention as defined by theclaims. It should be further understood that the terms “comprises”and/or “comprising” when used in this specification is taken to specifythe presence of stated features, integers, steps, operations, elements,and/or components, but does not preclude the presence or addition of oneor more other features, integers, steps, operations, elements,components, and/or groups thereof. As used herein, the term “and/or”includes any and all combinations of one or more of the associatedlisted items. Like reference numbers signify like elements throughoutthe description of the figures.

The present invention may be embodied as systems, methods, and/orcomputer program products. Accordingly, the present invention may beembodied in hardware and/or in software (including firmware, residentsoftware, micro-code, etc.). Furthermore, the present invention may takethe form of a computer program product on a computer-usable orcomputer-readable storage medium having computer-usable orcomputer-readable program code embodied in the medium for use by or inconnection with an instruction execution system. In the context of thisdocument, a computer-usable or computer-readable medium may be anymedium that can contain, store, communicate, propagate, or transport theprogram for use by or in connection with the instruction executionsystem, apparatus, or device.

The computer-usable or computer-readable medium may be, for example butnot limited to, an electronic, magnetic, optical, electromagnetic,infrared, or semiconductor system, apparatus, device, or propagationmedium. More specific examples (a nonexhaustive list) of thecomputer-readable medium would include the following: an electricalconnection having one or more wires, a portable computer diskette, arandom access memory (RAM), a read-only memory (ROM), an erasableprogrammable read-only memory (EPROM or Flash memory), an optical fiber,and a portable compact disc read-only memory (CD-ROM). Note that thecomputer-usable or computer-readable medium could even be paper oranother suitable medium upon which the program is printed, as theprogram can be electronically captured, via, for instance, opticalscanning of the paper or other medium, then compiled, interpreted, orotherwise processed in a suitable manner, if necessary, and then storedin a computer memory.

Embodiments of the present invention are described herein in the contextof digital subscriber line (DSL) technology for purposes ofillustration. It will be understood that the present invention is notlimited to DSL technology. Indeed, other communication technologiesand/or network configurations, such as, but not limited to, asynchronoustransfer mode (ATM), frame relay, hybrid fiber coax (HFC), wirelessbroadband, and/or Ethernet may also be used in other embodiments of thepresent invention. In general, the present invention is not limited toany communication technology and/or network configuration, but isintended to encompass any technology and/or network configurationcapable of carrying out operations described herein. Embodiments of thepresent invention are also described herein in the context of managingquality of service (QoS). As used herein, QoS includes, but is notlimited to, treatment applied to an access session, application flow,and/or packet with respect to scheduling a resource, bandwidthallocation, and/or delivery target in an individual element or across anend-to-end system.

As used herein, the term “protocol” refers to a defined set of rulesthat govern the exchange of data or information between two or moreentities. In addition, a “protocol layer” refers to the hierarchicalprotocol structure represented by the open systems interconnection (OSI)model developed by the International Organization for Standardization inwhich layer one corresponds to the physical layer, layer two correspondsto the data link layer, layer three corresponds to the network layer,layer four corresponds to the transport layer, layer five corresponds tothe session layer, layer six corresponds to the presentation layer, andlayer seven corresponds to the application layer.

The detailed description of embodiments of the present invention isorganized as follows:

1. Overview

2. Introduction

2.1 Purpose and Scope

2.2 Key Terms

3. Review of TR-059 Concepts

3.1 Network Service Provider Network

-   -   3.1.1 Description

3.2 Application Service Provider Network

-   -   3.2.1 Description    -   3.2.2 Capabilities

3.3 Regional Access Network

-   -   3.3.1 Broadband Remote Access Server    -   3.3.2 Access Network    -   3.3.3 Access Node

3.4 Evolution of the DSL Network

-   -   3.4.1 Access Session Types        4. QOS Capabilities of the Application Framework

4.1 General Approach

4.2 Classification

4.3 Business Models for Supporting Concurrent NSP and ASP AccessSessions

-   -   4.3.1 Simple Bandwidth Partitioning    -   4.3.2 Priority and Dynamic Bandwidth Sharing

4.4 Considerations Associated with this Approach

-   -   4.4.1 Static Classifiers    -   4.4.2 Queue Structure        5. Reference Data Model

5.1 Subscriber Maintained Data

5.2 Routing Gateway

5.3 Regional/Access Network

5.4 Application Service Provider

5.5 Network Service Provider

6. Reference Interface Specification and Detailed Message Flow

6.1 Interface Between RG and Regional/Access Network

6.2 Interface Between Regional/Access Network and ASP

6.3 Interface Between Regional/Access Network and NSP

6.4 Application Framework Infrastructure

-   -   6.4.1 Framework Infrastructure Element Functional Description    -   6.4.2 DSL Service Messaging Flow        7. Future Capabilities of the Application Framework        8. Example Use Scenario—Turbo Button        9. Example Use Scenario—Video Conferencing        10. Example Use Scenario—Gaming        11. Modifying Bandwidth and/or QoS in a Core Network        1. Overview

This document defines a common application framework built on top of theDSL Forum TR-059 reference architecture that can be used in a common wayto enable service providers to leverage bandwidth and QoS capabilitiesin the Regional/Access Network. This framework comprises an interfacespecification and associated data model and mechanisms to control theQoS and bandwidth capabilities defined in TR-059. A common interface forApplication Service Providers (ASPs) and Network Service Providers(NSPs) to leverage may reduce development costs and time to market. Thisinterface defines a mechanism for applications to request IP QoS andbandwidth from the DSL Regional/Access network.

2. Introduction

2.1 Purpose and Scope

Recent work in the DSL Forum has documented a reference architecture,DSL Evolution—Architecture Requirements for the Support of QoS-EnabledIP Services (TR-059), with the purpose of defining a common way ofsupporting enhanced IP applications by enabling IP QoS and bandwidthmanagement capabilities. TR-059 defines a common deploymentarchitecture, set of interface specifications, and fundamental networkelement requirements. The architecture and requirements are largely“transport or network” layer focused. It may be useful to complementthis work by defining a common higher-layer framework that leverages thecapabilities of TR-059 and that can be used by application serviceproviders (ASP) as they develop and deploy applications.

This document defines a common application framework built on top of theTR-059 reference architecture that can be used in a common way to enableservice providers to leverage bandwidth and QoS capabilities in theRegional/Access Network. This framework comprises an interfacespecification and associated data model and mechanisms to control theQoS and bandwidth capabilities defined in TR-059. A common interface forASPs and NSPs to leverage may reduce development costs and time tomarket. This interface defines a mechanism for applications to requestIP QoS and bandwidth from the DSL Regional/Access network.

Specifically, the application framework is based on the capabilitiesdefined in phase 2 of TR-059. Therefore, the framework defined hereassumes that the capabilities of the access node in the Regional/Accessnetwork will remain largely unchanged, but does leverage a policyapproach for provisioning the BRAS and Routing Gateway (RG) to manage IPflows appropriately. As real-time signaling capabilities becomeavailable this framework may be modified to support these capabilities.In defining the framework and providing details of its use, thisdocument also intends to demonstrate that capabilities defined (here andin TR-059) are sufficient to support a reasonable set of applications.

Services that span Regional/Access networks and requireinter-Regional/Access network communication are generally not describedherein as part of this framework. Support of these services is possibleif handled at the application layer where an ASP communicates to eachRegional/Access network to establish bandwidth and QoS for a service.

2.2 Key Terms

The following definitions apply for the purposes of this document:

Access Network The Access Network encompasses the elements of the DSLnetwork from the NID at the customer premises to the BRAS. This networktypically includes one or more Access Node type and often an ATMswitching function to aggregate them.

Access Node The Access Node contains the ATU-C, which terminates the DSLsignal, and physically can be a DSLAM, Next Generation DLC (NG-DLC), ora Remote Access Multiplexer (RAM). A DSLAM hub can be used in a centraloffice to aggregate traffic from multiple remote physical devices, andis considered logically to be a part of the Access Node. When the term“DSLAM” is used in this document, it is intended to very specificallyrefer to a DSLAM, and not the more generic Access Node. The Access Nodeprovides aggregation capabilities between the Access Network and theRegional Network. It is the first point in the network where traffic onmultiple DSL lines will be aggregated onto a single network.

Application Flow The set of packets associated with a particularapplication (e.g., video conferencing session, VoIP call, etc.).

Application Framework A common reference data model and interfacespecification built on top of the TR-059 reference architecture that canbe used in a common way to enable service providers to leveragebandwidth and QoS capabilities in the Regional/Access Network.

Auto Configuration Server (ACS) A data repository that allows theRegional/Access network to provide configuration information to RoutingGateways (RG) in Customer Premises

Broadband Remote Access Server (BRAS) The BRAS is the aggregation pointfor the subscriber traffic. It provides aggregation capabilities (e.g.,EP, PPP, ATM) between the Regional/Access Network and the NSP or ASP.Beyond aggregation, it is also the injection point for policy managementand IP QoS in the Regional/Access Networks.

Core Network The center core of the Regional Network. The functionscontained herein are primarily transport oriented with associatedswitching or routing capabilities enabling the proper distribution ofthe data traffic.

Downstream The direction of transmission from the ATU-C (Access Node) tothe ATU-R (modem).

Edge Network The edge of the Regional Network. The Edge Network providesaccess to various layer 2 services and connects to the Regional Networkcore enabling the distribution of the data traffic between various edgedevices.

Loop A metallic pair of wires running from the customer's premises tothe Access Node.

Many-to-Many Access Sessions The ability for multiple individual usersor subscribers, within a single premises, to simultaneously connect tomultiple NSPs and ASPs.

Regional Network The Regional Network interconnects the Network ServiceProvider's network and the Access Network. A Regional Network for DSLconnects to the BRAS, which is technically both in the Regional Networkand in an Access Network. Typically, more than one Access Network isconnected to a common Regional Network. The function of the RegionalNetwork in this document goes beyond traditional transport, and mayinclude aggregation, routing, and switching.

Regional/Access Network The Regional and Access Networks—grouped as andend-to-end QoS domain and often managed by a single provider. The followfunctional elements are contained in this network: Access Node, BRAS,and the ACS. Moreover, the Regional/Access Networks may also includecore network elements, such as routers.

Routing Gateway A customer premises functional element that provides IProuting and QoS capabilities. It may be integrated with or be separatefrom the ATU-R.

Rate Limit A means to limit the throughput of a particular PPP sessionor application flow by either buffering (shaping) or dropping (policing)packets above a specified maximum data rate. The term bandwidth is usedinterchangeably with the concept of rate limiting. The bandwidthallocated to a PPP session or application is determined by the ratelimit applied.

Session Session is typically an overloaded term. In this document it isintended to reference a PPP access session rather than a particularapplication flow.

Subscriber Used to refer to the person that is billed for a service,like NSP access service or ASP services. The subscriber is consideredthe primary user of the service (see the definition of “user” below) andis the main account contact. The subscriber to an NSP access is referredto as a Network Subscriber and the subscriber to an application isreferred to as an Application Subscriber.

Upstream The direction of transmission from the ATU-R (modem) to theATU-C (Access Node).

User The person or entity that receives the benefit of a given service.The user may or may not be the subscriber of the service. A subscribedservice has one or more users associated with the subscriber.

3. Review of TR-059 Concepts

To provide a common reference for the application framework, anarchitectural view of the DSL network is provided. The text in thissection is taken from TR-059 and provides a high level overview. For amore complete description refer to TR-059. FIG. 1 illustrates thecurrent state of deployed DSL networks. Boxes in the figures representfunctional entities—networks and logical components rather than physicalelements.

This traditional architecture is centered on providing service to a lineor a loop. It is desired, however, to be able to provide services thatare user-specific. Additionally, more than one subscriber can be presentat the same premises and share a single loop. TR-059 describes aslightly more complex situation, and hides the common complexity sharedwith FIG. 2.

FIG. 2 illustrates the components of a DSL access-based broadbandnetwork. FIG. 2 indicates ownership of the components by differentproviding organizations. Boxes in the figures represent functionalentities—networks and logical components rather than physical elements.

This model illustrates an architecture that provides services that areuser-specific, i.e., more than one subscriber can be present at the samepremises and share a single loop. Note that FIG. 2 shows many-to-manyaccess through a common Regional/Access network. It is used tosimultaneously provide an Application Service₁ between an ASP Network₁and User₁ at the same time and over the same U interface as it supportsa Network Service₂ between NSP Network₂ and User₂.

3.1 Network Service Provider Network

-   -   3.1.1 Description

The Network Service Provider (NSP) is defined as a Service Provider thatrequires extending a Service Provider-specific Internet Protocol (EP)address. This is the typical application of DSL service today. The NSPowns and procures addresses that they, in turn, allocate individually orin blocks to their subscribers. The subscribers are typically located inCustomer Premises Networks (CPNs). The NSP service may besubscriber-specific, or communal when an address is shared using NetworkAddress Port Translation (NAPT) throughout a CPN. This relationshipamong the NSP, A10-NSP interface, and Regional/Access Network is shownin FIG. 2. NSPs typically provide access to the Internet, but may alsoprovide access to a walled garden, VPN, or some other closed group orcontrolled access network. L2TP and IP VPNs are typical A10-NSPinterface arrangements.

The capabilities of the NSP may include, but are not limited to, forexample: authenticating network access between the CPN and the NSPnetwork; assignment of network addresses and IP filters; assignment oftraffic engineering parameters; and/or customer service andtroubleshooting of network access problems

3.2 Application Service Provider Network

-   -   3.2.1 Description

The Application Service Provider (ASP) is defined as a Service Providerthat uses a common network infrastructure provided by theRegional/Access Network and an IP address assigned and managed by theRegional Network Provider. This is a new type of DSL service. TheRegional Network Provider owns and procures addresses that they, inturn, allocate to the subscribers. ASPs then use this commoninfrastructure to provide application or network services to thosesubscribers. For example, an ASP may offer gaming, Video on Demand, oraccess to VPNs via IPsec or some other IP-tunneling method. The ASPservice may be subscriber-specific, or communal when an address isshared using NAPT throughout a Customer Premises Network (CPN). It isenvisioned that the ASP environment will have user-level rather thannetwork-access-level identification, and that a common LightweightDirectory Access Protocol (LDAP) directory will assist in providing useridentification and preferences. Logical elements used by ASPs typicallyinclude routers, application servers, and directory servers. Therelationship between the ASP Network, the A10-ASP interface, and theRegional Network is shown in FIG. 2.

-   -   3.2.2 Capabilities

The capabilities of the ASP may include, but are not limited to, forexample: authenticating users at the CPN; assignment of QoS to servicetraffic; customer service and troubleshooting of network access andapplication-specific problems; and/or ability to determine traffic usagefor accounting purposes and billing.

3.3 Regional Access Network

The Regional/Access Network comprises the Regional Network, BroadbandRemote Access Server, and the Access Network as shown in FIG. 3. Itsprimary function is to provide end-to-end data transport between thecustomer premises and the NSP or ASP. The Regional/Access Network mayalso provide higher layer functions, such as QoS and contentdistribution. QoS may be provided by tightly couplingtraffic-engineering capabilities of the Regional Network with thecapabilities of the BRAS.

-   -   3.3.1 Broadband Remote Access Server

The BRAS performs multiple functions in the network. Its most basicfunction is to provide aggregation capabilities between theRegional/Access Network and the NSP/ASP. For aggregating traffic, theBRAS serves as a L2TP Access Concentrator (LAC), tunneling multiplesubscriber Point-to-Point Protocol (PPP) sessions directly to an NSP orswitched through a L2TS. It also performs aggregation for terminated PPPsessions or routed IP session by placing them into IP VPNs. The BRASalso supports ATM termination and aggregation functions.

Beyond aggregation, the BRAS is also the injection point for providingpolicy management and IP QoS in the Regional and Access Networks. TheBRAS supports the concept of many-to-many access sessions. Policyinformation can be applied to terminated and non-terminated sessions.For example, a bandwidth policy may be applied to a subscriber whosePoint-to-Point (PPP) session is aggregated into an L2TP tunnel and isnot terminated by the BRAS. Sessions that terminate on (or are routedthrough) the BRAS, however, can receive per flow treatment because theBRAS has IP level awareness of the session. In this model, both theaggregate bandwidth for a customer as well as the bandwidth andtreatment of traffic per-application can be controlled.

-   -   3.3.2 Access Network

The Access Network refers to the network between the ATU-R and the BRASincluding the access node and any intervening ATM switches.

-   -   3.3.3 Access Node

The Access Node provides aggregation capabilities between the AccessNetwork and the Regional Network. It is the first point in the networkwhere traffic on multiple DSL lines will be aggregated onto a singlenetwork. Traditionally the Access Node has been primarily an ATMconcentrator, mapping PVCs from the ATU-R to PVCs in the ATM core. Ithas also shaped and policed traffic to the service access rates.

As described in TR-059, the responsibility of policing ATU-R to ATU-CPVCs to the subscribed line rate is moved from the Access Node to theBRAS to establish additional bandwidth on the DSL line for additionalservices. The Access Node sets the line rate for each PVC at the synchrate (or slightly less) of the ATU-R and ATU-C. This will make themaximum amount of subscriber bandwidth available for services. The BRASpolices individual sessions/flows as required to their required ratesand also performs the dynamic changes when bandwidth-on-demand servicesare applied.

3.4 Evolution of the DSL Network

Phases 1 and 2 of TR-059 introduce the capability to change theRegional/Access network from an IP unaware layer 2 network to a networkthat leverages IP awareness in key elements to enable IP QoS and moreefficient and effective use of bandwidth. These key IP aware elementsare the BRAS and the RG as shown in FIG. 4.

FIG. 4 represents a paradigm shift in that the BRAS and the RG are nowresponsible for managing the traffic flow through the network. Byenabling these devices to accept policy rules at subscriber session andapplication levels, IP flows can be managed in a more flexible and“dynamic” manner than previously possible. The BRAS is responsible formanaging IP traffic in the downstream direction such that traffic isscheduled according to priority and in a way that ensures thatcongestion in the downstream network is reduced (i.e., hierarchicalscheduling). The RG similarly, manages the scheduling of traffic in theupstream direction based on the priority of the session and/orapplication. Given that the RG cannot be trusted, the BRAS performs apolicing function to ensure the upstream bandwidth in the access networkis utilized appropriately. Note that the priority and bandwidth policiescan be applied at the PPP session and or application levels; therefore,there is flexibility in how traffic is treated in the network.

3.4.1 Access Session Types

The architecture also evolves the types and number of access sessions(specifically PPP sessions) that a subscriber would typically establishto a service provider. Where previously there had been just one accesssession to an ISP, there are now multiple access sessions with threebasic types:

Community NSP—Shown in FIG. 5 as the solid line between the RG and NSP₁,this type of access session is established between an RG and an NSP. Itis called the Community NSP connection because all the devices withinthe Customer Premises Network share the connection to the NSP using theNetwork Port Address Translation (NPAT) feature of the RG. Because theCommunity NSP connection is given the Default Route at the RG there cantypically be only one. This connection is typically set up to an ISP toprovide Internet access to all the devices in the Customer PremisesNetwork. This PPP session may terminate on the BRAS or may pass throughthe BRAS in tact and be placed into a L2TP tunnel to the NSP.

Personal NSP—Shown in FIG. 5 as the dashed line between User, and NSP₂,this type of access session is established between a device within theCustomer Premises Network and an NSP. It passes through the RG at theEthernet (PPPoE) level. It is called the Personal NSP connection becauseonly the device within the Customer Premises Network from which theconnection was established can access the NSP. This connection may avoidusing the NPAT feature of the RG. This connection is typically set up toan ISP or a corporation to provide private or personalized access, orany access that cannot traverse the NPAT sharing mechanism at the RG.This PPP session may terminate on the BRAS or may pass through the BRASin tact and be placed into a L2TP tunnel to the NSP.

ASP—Shown in FIG. 5 as the dotted line between the RG and ASP₁, thistype of access session is established between an RG and the ASP network.It is typically a single connection that is shared by all the ASPs.Because the Community NSP connection is typically given the DefaultRoute at the RG, the ASP connection must provide the RG with a list ofroutes to the ASP network. Also because there is not a default route tothe ASP network, it may not be possible to provide typical Internetaccess through the ASP connection. This connection is typically set upto the ASP network to provide application-specific and QoS-enabledaccess among all the applications in the ASP network and all the devicesin the Customer Premises Network. This PPP session type may terminate onthe BRAS so that per application flow treatment can be applied.

4. QOS Capabilities of the Application Framework

4.1 General Approach

TR-059 describes a hierarchical scheduling approach leveraged by theBRAS to manage the downstream links between the BRAS and the RG.Similarly, it describes how the BRAS leverages policing techniques(including a random discard enhancement) to apply backpressure to theupstream source to minimize potential congestion in that direction. Theapplication framework provides a mechanism for service providers tomodify bandwidth and QoS. In particular embodiments of the presentinvention, to simplify the number of queues to be managed in the BRASand RG, this framework assumes that only the ASP session has the abilityto support per application flow treatment. In such embodiments, NSPaccess sessions can only be managed in terms of the aggregate bandwidthand priority with respect to other access sessions on the DSL line.Because many ASPs share the ASP access session, the bandwidth andpriority of the session is set by the Regional/Access provider andtypically cannot be modified by an ASP. The ASP can however modify thecharacteristics of specific applications within the ASP PPP session byassigning the application to a particular queue and treatment type. TheBRAS and RG may schedule or police packets based on one or more of thefollowing parameters: the priority of the access session; the currentpacket's relation to the rate limit of the access session; the priorityof the application within the access session (only supported for the ASPPPP Session); and/or the current packet's relation to the rate limit ofthe application or queue, for example, an EF rate limit supported forthe ASP PPP session.

Network resources are typically not reserved in this model. Instead,traffic engineering policies and intelligent scheduling and policing ofpackets is leveraged to achieve aggregate QoS characteristics.Similarly, the Differentiated Services (Diffserv) model is leveraged asa way to classify, mark, and schedule packets. The QoS approach that hasbeen applied to the application framework assumes that thesecapabilities are in place and that QoS relationships can be viewedwithin a single subscribers DSL “connection” (ATM VC) between the BRASand the RG.

Further, if a pragmatic approach to providing QoS is taken, someadditional simplifying assumptions can be made. It is expected thatinitially there will only be a small number of applications requiringQoS. The expected applications include VoIP, video conferencing, videoon demand, and gaming. It is unlikely that the majority of DSL customerswill subscribe to all of these services and expect to use themsimultaneously. Rather, it is expected that only a small number ofapplications (e.g., 2 or 3) will need to be managed concurrently on aDSL line basis. The expected applications also imply a certain priorityrelationship among themselves. If while playing an Internet game a VoIPcall comes in, it may be generally agreed that the VoIP session shouldtake precedence over the gaming session (if finishing the game is moreimportant, then the user can choose not to answer the call). As long asthese assumptions hold true, then a small number of applications can bemanaged effectively with a small number of queues and a simple priorityarrangement among them. As the number of applications requiring QoSincreases, however, these assumptions may have to change and the QoSapproach may need to evolve to support a finer granularity.

The number of queues available for applications within the ASP PPPsession is five, in accordance with some embodiments of the presentinvention. This may change over time, in accordance with otherembodiments of the present invention, but initially the number of queuesis likely to be small. Diffserv like treatment is assumed whendescribing the queue behaviors and can be classified as one expeditedforwarding (EF) queue, up to 3 assured forwarding (AF) queues or onebest effort (BE) queue. The EF queue typically receives the highestpriority and is typically served first. This queue type is defined forconstant bit rate type servers. A rate limit associated with this queueis put in place so it should not be able to consume all the DSL lineresources. This queue will likely be reserved for voice applications. AFqueues are defined for traffic that is more variable in nature and wouldbe inefficient to associate with a fixed amount of network resources(EF). Queues in this category could receive different levels of priorityor could simply be used as an aggregate priority but each queue may havea different rate limit applied depending on the requirements of theapplication using that queue. To simplify the approach, the frameworkinitially assumes the later case where AF queue receive a “medium”priority treatment and the different queues are used to providedifferent bandwidth needs (i.e. rate limits). A BE queue is the defaultqueue and has resources available to it only after packets that are inprofile for the EF and AF queue are served.

The approach to establishing QoS and bandwidth requirements in thenetwork is one of provisioning rather than signaling. The BRAS and RGwill be provisioned with the classifiers to identify flows and queuethem appropriately. As a result the services that this model supportsare services that fit more into a subscription model rather than aninstantaneous establishment of service and QoS. This potentialdisadvantage, however, does not have to be apparent to the end users.Many services may require that the customer establish an account andperhaps even require the shipment of special hardware or software, forexample, VoIP Phone, PC camera, and the like. During the time frame thatthe customer is establishing service with the ASP, the DSL network canbe provisioned to support the service. It is important to note that theprovisioning time lines are not expected to be in terms of days, butcould be as small as a few minutes depending on how the applicationframework is implemented.

Given that a signaled approach to QoS is not included in the frameworkof certain embodiments of the present invention, real-time admissioncontrol cannot be accomplished at the network layer in such embodiments.While it could be possible to block the subscription of a new servicebased on the current, subscribed services, such a model may be toorestrictive because it does not allow the user to subscribe to twoapplications that they would not intend on using simultaneously.Instead, a strict priority relationship among the applications flows isused to manage simultaneous application interactions. Rate limits arealso applied at the RG and BRAS so that no single application canconsume all the subscriber's DSL resources and to provide some level offairness. An example application relationship, in accordance with someembodiments of the present invention, is shown in FIG. 6 and Table 1. Inthis example, it is assumed that the NSP and PNSP sessions receive besteffort treatment with respect to traffic that is in profile for the EFand AF queues in the ASP session. Other business models are possible asdescribed in Section 4.3. TABLE 1 Example Application PriorityRelationship within the ASP Session Rate Limit Application Queue of theQueue Classification Parameters VoIP Signaling High Priority 100 KbpsSIP Proxy IP Address & SIP Bearer High Priority 100 Kbps Gateway IPAddress & RTP Video Conf Control High Priority 100 Kbps SIP Proxy IPAddress & SIP Stream Audio/Voice High Priority 100 Kbps DSCP & MCU IPAddress& RTP Video Medium 384 Kbps DSCP & MCU IP Priority Address & RTPGaming Medium 100k Gaming Server IP Address Priority HTTP Low PriorityNone Default

FIG. 6 illustrates a queuing arrangement where there are five queues(EF, AF₁, AF₂, AF₃, and BE) within the ASP session for per applicationtreatment. In this arrangement, these queues can be characterized ashigh (EF), medium (AFs), and low priority (BE) treatment. Table 1illustrates that voice will receive strict priority over otherapplications. Rate limits can be applied to each of the applications toensure that a single application cannot starve out all otherapplications, but this requires dedicating a queue to each rate-limitedapplication. Priority alone may not resolve all of the possibleapplication interactions. In the example above, both the gaming andvideo conferencing video stream have the same priority. In the case thatboth applications are active they would compete over the first 100k ofbandwidth available to the medium priority class. The rate limitassociated with the AF₂ queue allows the video conferencing applicationto take precedence over the remaining resources up to its queue's ratelimit. If the user experience for either the video stream or the game isunacceptable, the user will have to make their own admission controldecision and pause or shut down the one they wish to have lowerpriority.

4.2 Classification

There are two basic levels of classification that need to be applied inthe framework: The first level is at the PPP session level.Classification at this layer is accomplished through inspection of theFully Qualified Domain Name (FQDN) used when the PPP session isinitiated. The second level is at the application layer—according toflows. To provide an application flow with the proper schedulingtreatment, it is desirable to easily classify the flow. Classificationof application flow may be accomplished using the header fields of theIP or Ethernet Packet (e.g., IP 5 tuple, DSCP, 802.1p). Using theinterface specified in Section 6, ASPs may communicate theclassification information that is used in the BRAS and RG. This sameinterface may be used to communicate the priority and desired bandwidth(rate limit) to be associated with the classifier. In certainembodiments of the present invention, this information is communicatedat subscription time, and is not intended to be established dynamicallyon a per-flow basis. As a result in such embodiments, the classificationinformation is expected to be static. The ASP may provide a well knownIP address, protocol, and/or Port to be used for classificationpurposes.

In particular embodiments of the present invention, within the customerpremises network (CPN), the CPE will be assigned private IP addressesfrom the RG. When traffic leaves the CPN, the RG will perform NPATenabling public routing of the packets. The use of private addressespresents two issues: Given that the CPE behind the RG will be usingdynamic private addresses, they cannot be used as part of theclassification parameters. Secondly, many applications require signalingmessages to convey dynamic IP addresses and port numbers of mediareceivers in their payloads. Existing static IP/transport layer policiesmay not be adequate in supporting session endpoints separated by NAT andfirewall entities. Therefore, Application Layer Gateway (ALG)capabilities may be required at the RG for opening and closing pinholesin the firewalls and maintaining the proper address translations fordynamically created ports associated with flows created by sessionendpoints. Some considerations with regard to ALG capabilities arediscussed in the next sections.

The BRAS can associate the IP address or ATM PVC of the RG with asubscriber and then use the ASP's address to match the source ordestination address of the packets to properly classify the flow. At thecustomer premises, the RG can match the ASP's address as the means ofclassifying the flow. Therefore, only the ASPs IP address (and possiblyport and protocol identifier) may be required for the bi-directionalflow to be classified correctly.

Certain types of applications may require additional information tocapture the flow. For these types of applications, the endpoints mayneed to provide additional classification information in the IP packetheader by marking the diffserv code point. The use of diffserv codepoints (DSCP) may be standardized which may allow the application tointelligently mark packets based on the expected treatment in thenetwork. DSCPs assigned by an untrusted entity can only be used aftersome edge device has performed a check on the classification of thepacket to ensure that it was marked correctly. The RG may not beconsidered a trusted element and, therefore, the BRAS may need to policeany classification performed by the RG—rather than simply accepting theDSCP that was provided. Depending on the relationship to the ASP, theRegional/Access network may be able to trust packets marked by the ASP.If the ASP is not trusted, either the BRAS or some other edge device mayneed to police the DSCPs.

4.3 Business Models for Supporting Concurrent NSP and ASP AccessSessions

FIG. 7 illustrates several bandwidth relationships that can exist on anADSL access loop. In FIG. 7, the outer circle represents the totalbandwidth that is available within a virtual circuit on an ADSL lineafter the modems have been allowed to sync to a higher rate than isconventional. Within this total bandwidth there are two access sessionsshown: an ASP Access Session and a NSP Access Session. The NSP AccessSession, shown in light horizontal stripes, occupies a smaller spacethan the whole Virtual Circuit. This indicates that the NSP accesssession is not allowed to access the total bandwidth on the VirtualCircuit. Conventionally, the NSP Session and the Virtual Circuit wouldhave been the same bandwidth. By increasing the sync rate on the DSLmodems, additional bandwidth is created that exceeds that which the NSPhas purchased.

The ASP access session has essentially the same set of bandwidth as theVirtual Circuit. This would indicate that some set of conditions existwhere the ASP session could occupy all the bandwidth on the ADSL line.Several Applications are shown overlaid on the sessions and within thebandwidth limits assigned to the NSP and ASP. The NSP application (darkhorizontal stripes) is a strict sub-set of the NSP Session and is usinga large fraction of the NSPs allowed bandwidth. The three otherapplications, however, show three salient relationships and businessmodels that can exist between applications in the ASP network and bothapplications as well as the access session for the NSP. Theserelationships will be described in the sections that follow.

-   -   4.3.1 Simple Bandwidth Partitioning

The first example is the Headroom Application and is shown in verticalstripes. This application is allowed to make use of only that bandwidththat the NSP could never access. In this type of model, a NSP isprovided a dedicated amount of bandwidth on the access loop—even ifthere is not dedicated bandwidth through the access network. In such anarrangement, ASP applications (or additional NSP access sessions) wouldonly receive bandwidth to which the modems could sync that was over andabove the rate sold to the NSP. In this arrangement, if the sync ratewere at or below the rate sold to the NSP, no additional applications oraccess sessions could be provided. This arrangement may be unnecessarilyrestrictive and may be difficult to implement.

The second example is the Sharing Application (shown checkered). Thisapplication has access to all the bandwidth described by the headroomapplication, but also has access to additional bandwidth sold to theNSP, but not currently in use by applications in the NSP Session. ASharing application can make use of all the bandwidth on the VC, but canonly use the “NSP” bandwidth when the NSP session is not using it.Unlike the previous model, this application can receive bandwidth evenwhen the sync rate is at or below the rate sold to the NSP. If the NSPapplications are making use of all their bandwidth, however, then theresult is similar to the arrangement described in the Headroomapplication. This arrangement could be described as work conserving, andmay be used for simple bandwidth partitioning.

-   -   4.3.2 Priority and Dynamic Bandwidth Sharing

The third example is the Competing Application (shown in transparentgray). In this example, the application may have access to some or allof the bandwidth used by the NSP and it may have access to thatbandwidth with greater, equal, or lesser precedence than the NSPapplications. Similarly, this application may also be able to pre-emptbandwidth that other ASP applications are attempting to use. This is themost complex arrangement, and the most flexible. A competing applicationcan compete for the bandwidth that NSP applications are attempting touse. Several cases of competing applications exist:

1. The first case is when a competing application has the sameprecedence as that of the NSP application(s). In this case, bandwidth isshared fairly according to a typical algorithm, like round-robin, orWeighted Fair Queuing (WFQ). Also, inter-application congestionavoidance mechanisms, like those that are part of TCP can decide howapplications would share bandwidth in this case.

2. A second case is when a competing application has greater precedencethan that of the NSP application(s). In this case, bandwidth is given tothe competing application in strict priority—only “left-over” bandwidthis provided to the other applications. This is the highest QoS level,and may be provided with an upper bound on the bandwidth that theapplication can obtain, i.e., a rate limit. If the application exceedsthe upper bound, its traffic will be dropped. This case is the mostapplicable to a VoIP application because it provides very low latencyand because VoIP is not bursty to the point that the rate limit would beexceeded.

3. A third case is when a competing application has a combination ofhigher precedence and equal precedence. A rate, such as a committedinformation rate (CIR), is set and the application gets the sametreatment as described in case 2 up to that rate. If the applicationbursts above CIR, then that traffic which bursts is treated differently;it must compete with the other applications as described in case 1.

4. A fourth case is when a competing application has a combination ofhigher precedence and lower precedence. A rate, such as a CIR, is setand the application gets the same treatment as described in case 2 up tothat rate. If the application bursts above CIR, then that traffic whichbursts is treated differently; it is treated like a sharingapplication—only receiving the leftover bandwidth that the NSPapplication does not use.

5. A fifth case is when a competing application has a combination ofhigher precedence, equal precedence and a strict rate limit. A rate,such as a CIR, and a second, higher rate, Peak information Rate (PIR),is set. The application gets the same treatment as described in case 3up to the PIR rate. If the application bursts above PIR, then thattraffic will be dropped.

6. Finally, there is a case when a competing application has acombination of higher precedence, equal precedence and lower precedence.As in case 5, a rate, such as a CIR, and a second, higher rate, such asa PIR, is set. The application gets the same treatment as described incase 3 up to the PIR rate. However, if the application exceeds the PIR,then that traffic is treated like a sharing application—only receivingthe bandwidth that the NSP does not use.

These treatments can also be provided among ASP applications and withfiner granularity among multiple applications.

4.4 Considerations Associated with this Approach

-   -   4.4.1 Static Classifiers        The following issues may be considered when using static        classifiers:

1. There can only be one class of treatment per application. There is nosense of individual users within the residence using the same service,but desiring different levels of service.

2. Dynamic, commutative peer-to-peer applications cannot be easilycaptured.

3. Applications with multiple flows between the same destinations cannotbe easily differentiated.

For applications like VoIP and video conferencing where the end pointsof a call may not be known a-priori, it is difficult to use a staticclassification scheme.

Below are several approaches to resolve these issues:

a. Force the application to some well-known IP address that can be usedfor classification purposes. This is true of a multipointvideoconference service that leverages a centralized (ASP provided) MCUor a VoIP call that is destined for a PSTN gateway or conference bridge.In both these cases, a static classifier can be used. This same approachcould be leveraged for on-net or point-to-point video calls. These callscould be routed to utilize an MCU, conference bridge, or PSTN gatewayeven though they are not required for any other reason other thanclassification. There are vendors in the marketplace that have developedproxy devices for this purpose. This may be less resource efficient,however, than allowing the calls to flow point-to-point.

b. Classify based on protocol used. For example, classification based onthe use of RTP could be used. Basing the classification on protocolalone, however, would enable other applications that use that sameprotocol to take advantage of QoS in the network without having to payfor it. Additionally, differentiation between application flows that usethe same protocol may not be achieved (e.g., voice and video using RTP).

c. Rely on the CPE to mark packets. In this case the IP phone or videoconference application emits packets marked with the proper diffservcode point so that the RG and BRAS can classify based on that marking.Any application choosing to mark their traffic, however, would be ableto take advantage of QoS in the network without having to pay for it.

d. QoS aware Application Layer Gateway (ALG). Similar to the way ALGshave been developed for allowing signals to traverse NPAT and firewallsby inspecting signaling messages, a QoS ALG may be created to inspectthe signaling packets for SDP messages and to dynamically createclassifiers during call setup. Given that initial signaling may bedestined for a well known address, (SIP proxy) the ALG can be staticallyconfigured to treat all RTP flows set up using a given SIPproxy—regardless of the actual communicating peers. As the ALG inspectsthe packets to modify the RG's firewall rules, it can also be used tomodify the RG's classification rules. This type of approach could beleveraged at the RG, where the number of sessions is small, but maypresent scaling issues if implemented in the BRAS.

e. Establish the classification information at call set up. This mayrequire complex real time signaling mechanisms to be in place in thenetwork to modify classifiers at call establishment and teardown.

Until a signaling approach is available, using an approach similar tothat described in (a) appears to be the most reasonable from atechnology and service offering perspective. A video conferencing ASPthat does not provide centralized Media Control Unit (MCU) capabilitiesmay only add limited value above that which is already available in themarket. In the near term, most VoIP calls will likely be destined forPSTN gateways, and this arrangement provides a simple way to classify.

Differentiating applications with multiple flows between the samedestinations, is typically seen within (but is not limited to)commutative services, like video conferencing. These applicationstypically have multiple flows (control/signaling, audio, and video)associated with a single application, and there may be a desire to treatthem differently. As long as they use different well-known IP addressesor protocol types, then a static classifier can be used. Unfortunately,when the same protocol type is used (e.g., RTP for both audio and video)then there may not be a way to differentiate those streams if they areboth destined for the same EP interface (e.g., MCU). Below are threeapproaches to resolve this issue:

a. Require applications to use separate IP interfaces that expectdifferentiated treatment. An MCU, for example, could define one IPinterface for video and another for audio. This would enable separateclassification in the upstream and downstream direction in the RG andBRAS. Depending on the direction of the flow, either the source ordestination can be used to match to the ASPs IP interfaces.

b. Rely on the application to mark packets. In this case, thevideoconference application emits packets marked to the proper diffservcode point so that the RG and BRAS could classify based on that marking.As long as the packets are being transmitted to a well-known address,the classifier can use the combination of the DSCP and the destinationIP. Given that there is a fixed IP address, no other applications wouldbe able to utilize the QoS intended for this application.

c. Rely on knowledge of the actual RTP ports used by each of the flowsto enable different treatments. This can be accomplished by staticallyassigning ports using a QoS ALG function as described above, or throughthe use of a signaling protocol.

-   -   4.4.2 Queue Structure

As the number of applications requiring QoS increases, so does thecomplexity of managing them in the access network. Over time, as moreand more ASPs deploy applications requiring QoS and bandwidthmanagement, the likelihood that multiple applications will be runningsimultaneously within the CPN may increase. The complexity of managingthese applications in a small number of queues with only three levels ofprecedence may become increasingly difficult given that there may nolonger be a well-defined priority relationship among them. One approachwould be to increase the number of queue types and behaviors. Diffservdefines four assured forwarding (AF) classes each with three levels ofdrop precedence. The addition of multiple AF classes to a strictpriority class (EF) and a low priority class (BE) already defined in theapplication framework can provide more granularity in queue andapplication behavior. It is unlikely, however, that the number of queuescan be scaled with the number of applications available.

While a limited number of additional queues may be available, theirexpected behavior may become increasingly complex to describe.Unfortunately, to make use of these additional behaviors, applicationsmust be able to define their requirements in a way that fits into thismodel. This becomes a challenge for two reasons: First, manyapplications do not understand that level of granularity andparticularly will not understand what other applications will be vyingfor the DSL line resources. Secondly, describing the inter-queue orinter-application behavior to ASPs so they can make use of thesecapabilities becomes more difficult as the number of queues increaseswithout strictly defining the amount of resources reserved per queue.This difficulty is in part the result of how diffserv was designed.Diffserv was not defined with the intent of managing per applicationflow behavior. Rather, it was defined to manage aggregate flow behaviorsin the core of the network. As the number of simultaneous applicationsincreases in the CPN and access network, the use of diffserv withoutresource reservation breaks down.

Leveraging a resource reservation approach can provide a mechanism formanaging increasing numbers of applications. The reservation scheme neednot necessarily require signaling. At subscription, time applicationscould reserve specific queues and could provide an intermediatesolution. Longer term, as the number of applications continues to grow,a more dynamic reservation of resources will be required. In the dynamiccase, applications may be able to reserve specific queues for theduration of the application flow, which will be released when they aredone. In doing so, admission control to the DSL resources can beprovided in a way that the applications behavior can be more clearlydescribed. Use of Resource Reservation Protocol (RSVP) would provide anexample of the former case. While having been defined for some time,actual RSVP implementations are elusive due to its general complexityand scaling limitations. Admission control provides one way to providean application dedicated resources or to provide an indication whenresources are not available. While conceptually attractive, it remainsunclear if the complexity of such an approach is feasible.

5. Reference Data Model

In this section a description of the data required in each of thefunctional domains of the architecture (Regional/Access Network, RG,ASP, NSP, and subscriber) is presented. FIG. 8 illustrates a high levelrepresentation of the relationships between the different domains inaccordance with some embodiments of the present invention. Based on thisabstract view of the domains involved in providing an end-to-endservice, a data model can be constructed.

Dotted lines 1 and 2 illustrated in FIG. 8 indicate that information isexchanged between the modules not specifically discussed with respect tothe interface reference model. The dashed lines illustrated in FIG. 8indicate a physical connection and the solid lines illustrated in FIG. 8indicate that information is exchanged within the scope of the interfacereference model. In particular, lines 1 and 2 illustrate exchangesbetween the subscriber and the NSP and ASP, respectively, when thesubscriber, for example, signs up for service. Line 3 illustrates theconfiguration of the RG by the Regional/Access Network. It will beunderstood that this may only be for the initial install. The ACSlocated with in the Regional/Access Network may handle all subsequentconfiguration changes. Line 4 illustrates the initiation of accesssessions that are terminated in the DSL network. The ACS located with inthe Regional/Access Network may communicate with the RG forconfiguration updates. Finally, lines 5 and 6 of FIG. 8 illustratecommunication between the NSP/ASP and the DSL network that establishes aDSL connection. The ASP and NSP may also communicate bandwidth and QoSchanges per session or application.

FIG. 9 depicts a UML model capturing the type of data used to supportbandwidth and QoS management in accordance with some embodiments of thepresent invention. This model is provided for illustration purposes onlyand is not intended to represent a complete deployment implementation,which may use a wider scope of information beyond bandwidth and QoS.FIGS. 10 through 12 provide additional details within the main domains,in accordance with some embodiments of the present invention, and aredescribed below. The remainder of this section provides a detaileddescription of the data records and attributes captured in the presentedUML model.

5.1 Subscriber Maintained Data

The following data elements are maintained at Subscriber Premises (thisrecord is maintained by the subscriber—it could be stored on a PC or anyother storage device/media) in accordance with some embodiments of thepresent invention: Record Type Elements Description Source NSPSubscriberThe subscribers need to know their PPP Session DSL_line_ID,NSPSubscriber_ID and Record NSPSubscriber_Password for accessing their970 NSP networks. Only a single NSP PPP session record can exist.DSL_Line_ID DSL_Line_ID is a unique identifier for the DSL DSL_Line_IDis provided line. Currently the TN is used as such an by theRegional/Access identifier. Network Provider at subscription time.NSPSubscriber_ID This ID is used for accessing the NSP networks.Assigned by the NSP at the time of subscription NSPSubscriber_(—)Subscriber_Password is initially set by the NSP, Initially assigned bythe Password later it can be changed by the Subscriber. It is NSP atsubscription time. used together with the NSPSubscriber_ID to Can bechanged by the access the NSP networks. subscriber. Personal Thesubscribers need to know their NSPSubscriber DSL_line_ID,PersonalNSPSubscriber_ID and PPP Session Personal NSPSubscriber_Passwordfor accessing Record their Personal NSP network. Multiple records 974can exist. DSL_Line_ID As defined above As defined above PersonalNSPThis ID is used for accessing the Personal NSP Assigned by the PersonalSubscriber_ID networks. NSP at the time of subscription.PersonalNSPSubscriber_(—) It is used together with the Initiallyassigned by the Password PersonalNSPSubscriber_ID to access the PNSPPNSP at the time of networks. subscription. Can be changed by thesubscriber. ASPSubscriber The subscribers need to know their PPP SessionDSL_line_ID, ASPSubscriber_ID and Record ASPSubscriber_Password foraccessing their 972 ASP services. For each application they subscribeto, they need to maintain their User_ID and Password. Only one ASP PPPsession record can exist. DSL_Line_ID As defined above As defined aboveASPSubscriber_ID This ID is used for accessing the ASP networks.Provided by ASP at the time of subscription ASPSubscriber_(—) It is usedtogether with the ASPSubscriber_ID to Initially assigned by ASP Passwordaccess the ASP networks. at the time of subscription. Can be changed bythe subscriber. User Account This record is maintained by user/users ofCreated at the time of Record services provided over the Regional/Accesssubscription to ASP 976, 978, 980 Network. A user account is tied to asubscriber services account. Multiple user accounts can be associatedwith a single subscriber account. Note: There is one or multiple UserAccount Record under each of the NSPSubscriber PPP Session Record,Personal NSPSubscriber PPP Session Record, and ASPSubscriber PPP SessionRecord. User_ID This ID is used for accessing the given service.Assigned by a given ASP to a particular user at the time subscriptionUser_Password It is used together with the User_ID to access a Initiallyassigned by a given service, given ASP to a particular user at the timeof subscription. Can be changed by the subscriber.

5.2 Routing Gateway

Routing Gateway is a customer premises functional element that providesEP routing and QoS capabilities. The main functions of the RG mayinclude one or more of: IP routing between the CPN and the AccessNetwork; multi-user, multi-destination support (Multiple simultaneousPPPoE sessions (started from the RG or from devices inside the CPN) inconjunction with non-PPP encapsulated EP (bridged) sessions); networkAddress Port Translation (NAPT); PPPoE pass though; multiple queues withscheduling mechanism; and/or IP QoS.

The following data elements are maintained at the RG in accordance withsome embodiments of the present invention: Record Type ElementsDescription Source Routing Routing Gateway Record is maintained by RG.It is initialized with the initial Gateway Record configuration by themanufacturer 902 or configured by the user during the install process.The ACS can also update this record during and after the initialinstall. DSL_Line_ID As defined above As defined above DSL_Sync_RateDSL_Sync_Rate is the current physical layer It is populated by RG duringmodern synch rate of the DSL line. This record training. includes bothupstream and downstream metrics. It also includes what is the maximumobtainable synch rate NSP PPP NSP PPP Session Record is maintained bythe Session Record RG to store information specific to the 904 communityNSP access session. This session is launched by the RG and provides theCPN with a default route. Only one community NSP record can exist.NSPSubscriber_ID This ID is used for accessing the DSL and NSP Assignedby NSP at subscription networks. time. NSPSubscriber_Password It is usedtogether with the Subscriber_ID to NSPSubscriber_Password is initiallyaccess the DSL and NSP networks. set by the NSP, later it can be changedby the Subscriber. Session_Classifier This parameter containsclassification This value is populated based on parameters to identifythe NSP PPP session configuration data received from the (i.e. Ethertypeand FQDN). ACS. Session_Priority Optional - Indicates the priority levelof the This value is populated based on NSP PPP connection relative tothe other PPP configuration data received from the sessions present -only required if DSL ACS. bandwidth is shared across PPP sessions andneed to establish a priority relationship across the PPP sessionsSession_Bandwidth The Session_Bandwidth contains information This valueis initialized based on a about the maximum bandwidth assigned to thisdefault value or on the Profile Data NSP PPP access session. receivedfrom the ACS. ASP PPP ASP PPP Session Record is maintained by theSession Record RG to store information specific to the ASP 906 accesssession. This PPP session is launched by the RG and receives routes, viaRIP, to the ASP network. Only one ASP record can exist. ASPSubscriber_IDThis ID is used for accessing the ASP network Assigned by ASP atsubscription (and potentially ASP applications although the time RGwould not be involved). ASPSubscriber_Password It is used together withthe ASPSubscriber_ID Initially set by the ASP, later it can to accessthe Regional/Access Network. (and be changed by the Subscriberpotentially ASP applications although the RG would not be involved)Session_Classifier This parameter contains classification This value ispopulated based on parameters to identify the ASP PPP sessionconfiguration data received from the (i.e. Ethertype and FQDN). ACS.Session_Priority Optional - Indicates the priority level of the Thisvalue is populated based on ASP PPP connection relative to the other PPPconfiguration data received from the sessions present - only required ifDSL ACS. bandwidth is shared across PPP sessions and need to establish apriority relationship across the PPP sessions Session_Bandwidth TheSession_Bandwidth contains information This value is populated based onabout the maximum bandwidth (upstream and configuration data receivedfrom the downstream) assigned to this ASP PPP access ACS. session.Application The Application Flow Record is maintained Flow Record by theRG for each application service that 910 subscriber or users of the DSLline subscribe to. It is used to store application specific data.Multiple application records can exist. Flow_Classifier Flow_Classifiercontains classification This value is populated based on parameters toidentify the application flow (IP configuration data received from the 5tuple). ACS. Flow_Priority Indicates the priority level of theapplication This value is populated based on within the ASP PPPconnection. This configuration data received from the parameterindicates the treatment of the ACS. application flow (what queue itshould be placed in) as well as any marking requirements (DSCP).Flow_Bandwidth Flow_Bandwidth parameter is assigned to the This value ispopulated based on given application based on the negotiated valueconfiguration data received from the between the ASP and theRegional/Access ACS. Network. It indicates the maximum upstream anddownstream bandwidth. It is used by the RG to shape and police theapplication flow. Personal NSP Personal NSP PPP Session Record is PPPSession maintained by the RG to store information Record specific to thePersonal NSP access session. 908 Multiple records can exist.Session_Classifier This parameter contains classification This value ispopulated based on parameters to identify the PNSP PPP sessionconfiguration data received from the (i.e. Ethertype and FQDN). ACS.Session_Priority Optional - Indicates the priority level of the Thisvalue is populated based on PNSP PPP connection relative to the otherPPP configuration data received from the sessions present - onlyrequired if DSL ACS. bandwidth is shared across PPP sessions and need toestablish a priority relationship across the PPP sessions.Session_Bandwidth The Session_Bandwidth contains information This valueis populated based on about the maximum bandwidth assigned to theconfiguration data received from the PNSP access service. ACS.

5.3 Regional/Access Network

The primary function of the RegionalAccess Network is to provideend-to-end data transport between the customer premises and the NSP orASP. The Regional/Access Network may also provide higher layerfunctions, such as QoS and bandwidth management. QoS may be provided bytightly coupling traffic-engineering capabilities of the RegionalNetwork with the capabilities of the BRAS.

The following data elements are maintained at the Regional/AccessNetwork in, for example, a Regional/Access Network Record 920 inaccordance with some embodiments of the present invention: Record TypeElements Description Source DSL Line Record The DSL line record ismaintained in the 922 Regional/Access Network and is unique to each DSLline. It maintains data specific to a DSL line and the sessions thattraverse it. DSL_Line_ID As defined above As defined above DSL_Sync_RateDSL_Sync_Rate is the current physical This data is obtained from thelayer synch rate of the DSL line. This DSLAM EMS and the RG recordincludes both upstream and downstream metrics. It also includes what arethe maximum obtainable data rates in either direction. NSP PPP SessionNSP PPP Session Record is maintained by Record the Regional/AccessNetwork to store 926 information specific to the community NSP PPPaccess sessions. The NSP access record is tied to the DSL Line Record.Only one can exist. SP_ID Uniquely identifies the NSP that the Assignedby the subscriber has a relationship with. Used to Regional/AccessNetwork cross reference users to NSPs who make Provider when a wholesaleturbo/QoS requests. relationship is established with the NSPSession_Classifier This parameter contains classification Provided bythe NSP at parameters to identify the NSP PPP session subscription time.(i.e. Ethertype and FQDN). Session_Priority Optional - Indicates thepriority level of the The Regional/Access Network NSP PPP connectionrelative to the other Provider initializes this value at PPP sessionspresent - only required if subscription time based on the DSL bandwidthis shared across PPP business model and type of sessions and need toestablish a priority wholesale access that is being relationship acrossthe PPP sessions sold to the NSP and its relationship to the ASP or thePNSP sessions. Session_Bandwidth The Session_Bandwidth contains Thisvalue is set by the NSP. information about the maximum bandwidth(upstream and downstream) assigned to this NSP PPP session. PersonalNSPPPP PersonalNSP PPP Session Record is Session Record maintained by theRegional/Access 930 Network to store information specific to thePersonal NSP PPP access sessions. Multiple records can exist. SP_ID Asdefined above As defined above Session_Classifier This parametercontains classification Provided by the NSP at parameters to identifythe PNSP PPP subscription time. session (i.e. Ethertype and FQDN).Session_Priority Optional - Indicates the priority level of the TheRegional/Access Network PNSP PPP connection relative to the otherProvider initializes this value at PPP sessions present - only requiredif subscription time based on the DSL bandwidth is shared across PPPbusiness model and type of sessions and need to establish a prioritywholesale access that is being relationship across the PPP sessions soldto the NSP and its relationship to the ASP or the PNSP sessions.Assigned by PNSP and passed to Regional/Access network via NNI messageinterface. Session_Bandwidth The Session_Bandwidth contains This valueis initially set by the information about the maximum bandwidth PNSP,(upstream and downstream) assigned to this PNSP PPP session. ASP PPPSession ASP PPP Session Record is maintained by Record theRegional/Access Network to store 928 information specific to the ASP PPPsession. The ASP PPP Record is tied to the DSL Line Record. Only one ASPrecord can exist. SP_ID As defined above As defined aboveSession_Classifier This parameter contains classification Provided bythe ASP at parameters to identify the ASP PPP session subscription time(i.e. Ethertype and FQDN). Session_Priority Optional - Indicates thepriority level of the The Regional/Access Network ASP PPP connectionrelative to the other Provider initializes this value at PPP sessionspresent - only required if subscription time based on the DSL bandwidthis shared across PPP business model and type of sessions and need toestablish a priority wholesale access that is being relationship acrossthe PPP sessions sold to the NSP and its relationship to the ASP or thePNSP sessions. Assigned by ASP and passed to Regional/Access network viaNNI message interface. Session_Bandwidth The Session_Bandwidth containsThis value is initially set by the information about the maximumbandwidth Regional/Access Network (upstream and downstream) assigned tothis Provider, but could be modified ASP PPP session. by individual ASPsthat request more bandwidth for their application. An alternative modelis that this value is set to the max value initially and ASPs onlyaffect their allotment of bandwidth within the PPP session. ApplicationFlow The Application Flow Record contains Record specific details aboutan application within 932 the ASP session. This record is tied to theASP account record. Many application records can be associated with anASP account record. Flow_Classifier Flow_Classifier containsclassification Values provided by the ASP. parameters to identify theapplication flow (IP 5 tuple). It is used by the BRAS & the RG.Flow_Priority Indicates the priority level of the Provided by the ASP.application within the ASP PPP connection. Regional/Access Network Thisparameter indicates the treatment of Provider provides available theapplication flow (what queue it should options to select. be placed in)as well as any marking requirements (DSCP). It is used by the BRAS andthe RG Flow_Bandwidth Flow_Bandwidth parameter is assigned to Thesevalues are provided by the given application based on the the ASP tomeet the needs of the negotiated value between the ASP and theapplication. Regional/Access Network. It indicates the maximum upstreamand downstream bandwidth. It is used by the BRAS & the RG to shape andpolice the application flow. Service Provider The service ProviderRecord is used to Record authenticate service providers (NSPs, 924 ASPs)who wish to query the Regional/Access Network for information and makebandwidth and or QoS requests. SP_ID As defined above As defined aboveSP_Credentials Used to authenticate this service provider Assigned bythe together with SP_ID when connecting to Regional/Access Network theRegional/Access Network. Provider Authorization Represents what recordsthe SP has access Assigned by the to (DSL line records can it makeRegional/Access Network queries/modifications to) Provider CDR_DataStores billing data for wholesale access to This data is generated bythe Turbo and QoS controls Regional/Access Network Provider

5.4 Application Service Provider

The Application Service Provider (ASP) is defined as a Service Providerthat shares a common infrastructure provided by the Regional/AccessNetwork and an IP address assigned and managed by the Regional NetworkProvider. In particular embodiments of the present invention, the ASPprovides one or more of: application services to the subscriber (gaming,video, content on demand, IP Telephony, etc.); service assurancerelating to this application service; additional software or CPE; and/ora contact point for all subscriber problems related to the provision ofspecific service applications and any related subscriber software.However, the ASP may not provide or manage the assignment of IP addressto the subscribers.

The following data elements may be maintained at the ASP in accordancewith some embodiments of the present invention: Record Type ElementsDescription Source ASP Record ASP Record is maintained by each serviceprovider. 960 This record contains the service provider's name,password, and other related information that identifies this unique ASPand is used to communicate with Regional/Access Network Provider. ASP_IDUsed to uniquely identify an ASP that has a business Assigned byrelationship with Regional/Access Network Regional/Access NetworkProvider. Provider at the time of connecting the ASP to the ASP network.ASP_Credentials Used to authenticate an ASP together with ASP_IDAssigned by when a service session is established with a Regional/AccessNetwork Regional/Access Network Provider. Provider at the time ofconnecting the ASP to the ASP network. ASP Subscriber ASP SubscriberRecord is maintained by ASP that Record provides the applicationservice. This record 962 uniquely identifies the subscriber and servicerelated data. DSL_Line_ID As defined above As defined aboveASPSubscriber_ID This ID is used for accessing the DSL and ASP Assignedby the ASP at the networks. time of subscription. ASPSubscriber_(—) Itis used together with the ASPSubscriber_ID to Assigned by the ASP at thePassword access the ASP application. time of subscription. Note: The ASPSubscriber ID and Password are only used by ASP for its own purpose andwill not be used or referenced by Regional/Access Network forauthentication purpose. It is just for maintaining ASP data integrity.Session_Classifier Local copy of Regional/Access Network ASP PPPAcquired from the Session Classification info. Regional/Access Networkthrough the ANI interface. Session_Priority Local copy ofRegional/Access Network ASP PPP Acquired from the Session Priority info.Regional/Access Network through the ANI interface. Session_BandwidthLocal copy of the Regional/Access Network ASP Acquired from the PPPSession Bandwidth Info. Regional/Access Network through the ANIinterface. Application Flow This record is maintained by the ASP andused to Control Record store application specific information such as966 bandwidth arrangement and QoS settings. This record is tied to theASP bandwidth Record. Multiple Application Record can be associated withone single ASP bandwidth record. Flow_Classifier Flow_Classifiercontains classification parameters Values provided by the ASP. toidentify the application flow (IP 5 tuple). It is used by the BRAS & theRG. Flow_Priority Indicates the priority level of the application withinProvided by the ASP. The the ASP PPP connection. This parameterindicates Regional/Access Network the treatment of the application flow(what queue it Provider specifies available should be placed in) as wellas any marking options to select. requirements (DSCP). It is used by theBRAS and the RG Flow_Bandwidth Flow_Bandwidth parameter is assigned tothe given These values are provided application based on the negotiatedvalue between by the ASP to meet the the ASP and the Regional/AccessNetwork Provider. needs of the application. It indicates the maximumupstream and downstream bandwidth. It is used by the BRAS & the RG toshape and police the application flow. ASP User Account This record ismaintained by the ASP. An ASP user 964 account is tied to an ASPsubscriber account. Multiple user accounts can be associated with asingle subscriber account. User_ID This ID is used for accessing thegiven service. Assigned by a given ASP to a particular user.User_Password It is used together with the User_ID to access aUser_Password is initially given service. assigned by an ASP. Can bechanged by the user.

5.5 Network Service Provider

The Network Service Provider (NSP) is defined as a Service Provider thatrequires extending a Service Provider-specific Internet Protocol (IP)address. This is the typical application of conventional DSL service.The NSP owns and procures addresses that they, in turn, allocateindividually or in blocks to their subscribers. The subscribers aretypically located in Customer Premises Networks (CPNs). The NSP servicemay be subscriber-specific, or communal when an address is shared usingNAPT throughout a CPN. The NSP may include Internet Service Providers(ISPs) and Corporate Service Providers (CSPs); may be responsible foroverall service assurance; may provide CPE, or software to run oncustomer-owned CPE, to support a given service; may provide the customercontact point for any and all customer related problems related to theprovision of this service; and/or may authenticate access and providesand manages the assignment of IP address to the subscribers.

The following data elements are maintained at the NSP in accordance withsome embodiments of the present invention: Record Type ElementsDescription Source NSP Record NSP Record is maintained by each NSP. This940, 950 record contains the service provider's name, password, andother related information that identifies this unique service providerand is used communicate with access NSP. NSP_ID Uniquely identifies theNSP that the subscriber Assigned by Regional/Access has a relationshipwith. Used to cross Network Provider at the time reference users to NSPswho make turbo/QoS of connecting the NSP. requests NSP_Credentials Usedto authenticate this NSP together with Assigned by Regional/AccessNSP_ID when a service session is established Network Provider at thetime with a DSL access network for requesting a of connecting the NSP.network service. NSP Subscriber NSP Subscriber Record is maintained byNSP Record that provides the network service. This record 942, 952uniquely identifies the subscriber and service related data. DSL_Line_IDAs defined above As defined above NSPSubscriber_ID This ID is used foraccessing the DSL and Assigned to a DSL subscriber NSP networks. by theNSP. NSPSubscriber_(—) It is used together with the NSPSubscriber_IDAssigned by the ASP at the Password to access the NSP application. timeof subscription. Note: The NSP Subscriber ID and Password are only usedby NSP for its own purpose and will not be used or referenced byRegional/Access Network for authentication purpose. It is just formaintaining the NSP data integrity. Session_Classifier Local copy ofRegional/Access Network NSP Acquired from the PPP Session Classificationinfo Regional/Access Network through the NNI interface. Session_PriorityLocal copy of Regional/Access Network NSP Acquired from the PPP SessionPriority info. Regional/Access Network through the NNI interface.Session_Bandwidth Local copy of the Regional/Access Network Acquiredfrom the ASP PPP Session Bandwidth Info. Regional/Access Network throughthe NNI interface. NSP User Account This record is maintained by theNSP. A NSP 944, 954 user account is tied to an NSP subscriber account.Multiple user accounts can be associated with a single subscriberaccount. User_ID This ID is used for accessing the given service.Assigned by a given NSP to a particular user. User_PasswordUser_Password is initially assigned by a NSP. Can be changed by theuser.6. Reference Interface Specification and Detailed Message Flow

This interface reference specification defines an interface between theRegional/Access Network and a Network Service Provider (NSP), a PersonalNSP (PNSP), and an Application Service Provider (ASP) as well as aninterface between the Regional/Access Network and Routing Gateway (RG)for enabling the NSP/PNSP/ASP to utilize the bandwidth and QoSmanagement capabilities provided by the Regional/Access Network in theirNSP/PNSP/ASP applications, in accordance with some embodiments of thepresent invention.

6.1 Interface Between RG and Regional/Access Network

This section defines the messaging interface between the Regional/AccessNetwork and the Routing Gateway, in accordance with some embodiments ofthe present invention. This interface does not define any message for RGor ACS authentication assuming both of them are part of the DSL Networkinfrastructure.

1. UpdateSessionBandwidthInfo(DSL_Line_ID, SP_ID, Session_Classifier,Session_Priority, Session_Bandwidth)

This message is sent from the Regional/Access Network to a specified RG(via ACS) as a notification when new bandwidth and QoS information for aPPP session becomes available. The bandwidth and QoS related parametersinclude Session_Classifier, Session_Priority, and Session_Bandwidth.These parameters will be stored in the NSP PPP Session Record, PNSP PPPSession Record, or ASP PPP Session Record depending on the SP_ID. Thesesession records are defined in the DSL Data Reference Model.

-   DSL_Line_ID: Subscriber's line identification.-   SP_ID: The identifier of service provider requesting for service.    The service provider can only be NSP, PNSP, or ASP.-   Session_Classifier: PPP session classifier.-   Session_Priority: Session priority indicator.-   Session_Bandwidth: Bandwidth data including upstream bandwidth and    downstream bandwidth.    2. UpdateSessionBandwidthAck(DSL_Line_ID, SP_ID)

This message is sent from the RG to the Regional/Access Network (viaACS) as an acknowledgement of receiving the update session bandwidthinformation notification.

-   DSL_Line_ID: Subscriber's line identification.-   SP_ID: The identifier of service provider requesting for service.    The service provider can only be NSP, PNSP, or ASP.    3. UpdateAppFlowControlInfo(DSL_Line_ID, SP_ID, Flow_Classifier,    Flow_Priority, Flow_Bandwidth)

This message is sent from the Regional/Access Network to a specified RG(via ACS) as a notification of new bandwidth and QoS info forapplication flow becoming available. The parameters includingFlow_Classifier, Flow_Priority, and Flow_Bandwidth will replace theexisting data stored in the Application Flow Control Record defined inthe Regional/Access Data Reference Model.

-   DSL_Line_ID: Subscriber's line identification.-   SP_ID: The identifier of service provider requesting for service.    The service provider can only be NSP, PNSP, or ASP.-   Flow_Classifier: Application flow classifier.-   Flow_Priority: Priority queue indicator.-   Flow_Bandwidth: Flow bandwidth information for shaping and policing.    4. UpdateAppFlowControlAck(DSL_Line_ID, SP_ID)

This message is sent from the RG to the Regional/Access Network (viaACS) as an acknowledgement of receiving the update application flowcontrol info notification.

-   DSL_Line_ID: Subscriber's line identification.-   SP_ID: The identifier of service provider requesting for service.    The service provider can only be NSP, PNSP, or ASP.    5. UpdateSessionBandwidthRequest(DSL_Line_ID, SP_ID)

This message is sent from the RG to the RegionalAccess Network (via ACS)as a request for obtaining the PPP session level of the bandwidth andQoS settings stored at the Regional/Access Network for the specifiedsubscriber line.

-   DSL_Line_ID: Subscriber's line identification.-   SP_ID: The identifier of service provider requesting for service.    The service provider can only be NSP, PNSP, or ASP.    6. UpdateSessionBandwidthResponse(DSL_Line_ID, SP_ID,    Session_Classifier, Session_Priority, Session_Bandwidth,    Return_Code)

This message is sent from the Regional/Access Network to the RG (viaACS) as a response for getting the PPP session level of the bandwidthand QoS settings request.

-   DSL_Line_ID: Subscriber's line identification.-   SP_ID: The identifier of service provider requesting for service.    The service provider can only be NSP, PNSP, or ASP.-   Session_Classifier: PPP session classifier.-   Session_Priority: Session priority indicator.-   Session_Bandwidth: Session bandwidth information including upstream    bandwidth and downstream bandwidth.-   Return_Code: Return code from the Regional/Access Network,    indicating if the request is accomplished successfully.    7. UpdateAppFlowControlRequest(DSL_Line_ID, SP_ID)

This message is sent from the RG to the Regional/Access Network (viaACS) as a request for obtaining the application flow level of thebandwidth and QoS settings stored at the RegionalAccess Network for thespecified subscriber line.

-   DSL_Line_ID: Subscriber's line identification.-   SP_ID: The identifier of service provider requesting for service.    The service provider can only be NSP, PNSP, or ASP.    8. UpdateAppFlowControlResponse(DSL_Line_ID, SP_ID, Flow_Classifier,    Flow_Priority, Flow_Bandwidth, Return_Code)

This message is sent from the RegionalAccess Network to the RG (via ACS)as a response for getting the application flow level of the bandwidthand QoS settings request.

-   DSL_Line_ID: Subscriber's line identification.-   SP_ID: The identifier of service provider requesting for service.    The service provider can only be NSP, PNSP, or ASP.-   Flow_Classifier: Application flow classifier.-   Flow_Priority: Priority queue indicator.-   Flow_Bandwidth: Flow bandwidth information for shaping and policing.-   Return_Code: Return code from the DSL Network, indicating if the    request is accomplished successfully.

6.2 Interface Between Regional/Access Network and ASP

This section defines the messaging interface between the Regional/AccessNetwork and the Application Service Providers, in accordance with someembodiments of the present invention.

1. EstablishServiceSessionRequest (SP_ID, SP_Credentials)

This message is sent from an ASP to the Regional/Access Network as arequest for establishing a communication session. All the ASPs need tobe authenticated by the Regional/Access Network before the networkbandwidth and QoS service capabilities can be accessed. With thisrequest, the ASP can specify a life span of this session by providing alife span parameter that could be imbedded in the SP_Credentials. Whenthe specified life span expires, the ASP must resend this request toestablish a new service session.

-   SP_ID: Service Provider Identification. SP_Credentials: Service    Provider Credentials.    2. EstablishServiceSessionResponse (Authorization, Return_Code)

This message is sent from the Regional/Access Network to the serviceprovider as a response for the communication session establishmentrequest. The Regional/Access Network returns an authorization codeindicating what services and resources are authorized for the serviceprovider to access.

-   Authorization: Authorization code indicating what Regional/Access    Network resources is authorized for the service provider to access.-   Return_Code: Return code from the Regional/Access Network,    indicating if the request is accomplished successfully.    3. CreateAppFlowControlRecordRequest (Authorization, DSL_Line_ID,    SP_ID, Flow_Classifier, Flow_Priority, Flow_Bandwidth)

This message is sent from an ASP to the Regional/Access Network as arequest for creating an application specific flow control record definedas Application Flow Control Record in DSL Data Model. The initialsettings are provided with Flow_Clasifier, SP_ID, Flow_Priority, andFlow_Bandwidth.

-   Authorization: Authorization code obtained when the service session    is established.-   DSL_Line_ID: Subscriber's line identification.-   SP_ID: The identifier of service provider requesting for service.    The service provider can only be ASP.-   Flow_Classifier: 5-tuple (source IP address, source port,    destination UP address, destination port, protocol type) identifying    a unique application flow.-   Flow_Priority: Priority queue setting-   Flow_Bandwidth: Flow bandwidth information for shaping and policing.    4. CreateAppFlowControlRecordResponse (DSL_Line_ID, Return_Code)

This message is sent from the Regional/Access Network to the ASP as aresponse for the creation of the application flow control recordrequest.

-   DSL_Line_ID: Subscriber's line identification.-   Return_Code: Return code from the Regional/Access Network,    indicating if the request is accomplished successfully.    5. DeleteAppFlowControlRecordRequest (Authorization, DSL_Line_ID,    SP_ID, Flow_Classifier)

This message is sent from an ASP to the Regional/Access Network as arequest for deleting an Application Flow Control Record defined in DSLData Model.

-   Authorization: Authorization code obtained when the service session    is established.-   DSL_Line_ID: Subscriber's line identification.-   SP_ID: The identifier of service provider requesting for service.    The service provider can only be ASP.-   Flow_Classifier: Identifier of an application flow.    6. DeleteAppFlowControlRecordResponse (DSL_Line_ID, Return_Code)

This message is sent from the Regional/Access Network to the ASP as aresponse for the deletion of the application flow control recordrequest.

-   DSL_Line_ID: Subscriber's line identification.-   Return_Code: Return code from the Regional/Access Network,    indicating if the request is accomplished successfully.    7. ChangeAppFlowControlRequest (Authorization, DSL_Line_ID, SP_ID,    Flow_Classifier, Flow_Priority, Flow_Bandwidth)

An ASP can send this message to the Regional/Access Network as a requestfor changing the Priority and Shaping Data defined in the ApplicationFlow Control Record of the DSL Data Model.

-   Authorization: Authorization code obtained when the service session    is established.-   DSL_Line_ID: Subscriber's line identification.-   SP_ID: The identifier of service provider requesting for service.    The service provider should be an ASP.-   Flow_Classifer: Application traffic flow identifier.-   Flow_Priority: The application priority queue indicator for    replacing the existing settings.-   Flow_Bandwidth: Flow bandwidth information for replacing the    existing settings.    8. ChangeAppFlowControlResponse (DSL_Line_ID, Return_Code)

This message is sent from the Regional/Access Network to the serviceprovider as a response for the bandwidth change request. A Return_Codeis sent back indicating whether the change is successful.

-   DSL_Line_ID: Subscriber's line identification.-   Return_Code: Return code from the Regional/Access Network,    indicating if the request is accomplished successfully.    9. QueryAppFlowControlRequest (Authorization, DSL_Line_ID, SP_ID,    Flow_Classifier)

An ASP can send this message to the Regional/Access Network as a requestfor querying the application specific priority and shaping informationcontained in the Application Flow Control Record.

-   Authorization: Authorization code obtained when the service session    is established.-   DSL_Line_ID: Subscriber's line ID.-   SP_ID: Identifier of the service provider requesting for bandwidth    and priority information.-   Flow_Classifier: Identifier of an application flow.    10. QueryAppFlowControlResponse (DSL_Line_ID, Flow_Classifier,    Flow_Priority, Flow_Bandwidth, Return_Code)

This message is sent from the Regional/Access Network to the serviceprovider as a response for the bandwidth info request. The bandwidthdata record is returned.

-   DSL_Line_ID: Subscriber's line identification.-   Flow_Classifier: Identifier of an application flow.-   Flow_Priority: Current priority queue setting.-   Flow_Bandwidth: Current bandwidth setting for shaping and policing.-   Return_Code: Return code from the Regional/Access Network,    indicating if the request is accomplished successfully.    11. QuerySessionBandwidthRequest (Authorization, DSL_Line_ID, SP_ID)

An ASP, can send this message to the Regional/Access Network as arequest for querying the PPP session bandwidth and priority informationassociated with the specified DSL_Line_ID. The data is stored in ASP PPPSession record defined in the DSL Data Model.

-   Authorization: Authorization code obtained when the service session    is established.-   DSL_Line_ID: Subscriber's line ID.-   SP_ID: Identifier of the service provider requesting for bandwidth    and priority information.    12. QuerySessionBandwidthResponse (DSL_Line_ID, Session_Classifier,    Session_Priority, Session_Bandwidth)

This message is sent from the Regional/Access Network to the serviceprovider as a response for the bandwidth info request. The bandwidthdata record is returned.

-   DSL_Line_ID: Subscriber's line identification.-   Session_Classifier: PPP session classifier used to identify PPP    session traffic flow.-   Session_Priority: Current Priority queue setting.-   Session_Bandwidth: Current session bandwidth setting.    13. TerminateServiceSessionRequest (SP_ID, Authorization)

This message is sent from an ASP to the Regional/Access Network as arequest for terminating a communication session.

-   SP_ID: Service Provider Identification.-   Authorization: Authorization code indicating what Regional/Access    Network resources is authorized for the service provider to access.    14. TerminateServiceSessionResponse (SP_ID, Return_Code)

This message is sent from the Regional/Access Network to the serviceprovider as a response for the communication session terminationrequest.

-   SP_ID: Service Provider Identification.-   Return_Code: Return code from the Regional/Access Network,    indicating if the request is accomplished successfully.

6.3 Interface Between Regional/Access Network and NSP

This section defines the messaging interface between the Regional/AccessNetwork and Network Service Provider, in accordance with someembodiments of the present invention.

1. EstablishServiceSessionRequest (SP_ID, SP_Credentials)

This message is sent from a NSP to the Regional/Access Network as arequest for establishing a communication session. The NSPs need to beauthenticated by the Regional/Access Network before the networkbandwidth and QoS service capabilities can be accessed. With thisrequest, the NSP can specify a life cycle of this session by providing alife span parameter imbedded in the SP_Credentials. When the specifiedlife span expires, the NSP must resend this request to establish a newservice session.

-   SP_ID: Service Provider Identification.-   SP_Credentials: Service Provider Credentials.    2. EstablishServiceSessionResponse (Authorization, Return_Code)

This message is sent from the Regional/Access Network to the serviceprovider as a response for the communication session establishmentrequest. The Regional/Access Network returns an authorization codeindicating what services and resources are authorized for the serviceprovider to access.

-   Authorization: Authorization code indicating what Regional/Access    Network resources is authorized for the service provider to access.-   Return_Code: Return code from the Regional/Access Network,    indicating if the request is accomplished successfully.    3. ChangeSessionBandwidthRequest (Authorization, DSL_Line_ID, SP_ID,    Session_Classifier, Session_Priority, Session_Bandwidth)

A NSP can send this message to the Regional/Access Network as a requestfor changing the PPP session bandwidth and priority informationassociated with the specified DSL_Line_ID. The data is stored in the NSPPPP Session Record defined in the DSL Data Model.

-   Authorization: Authorization code obtained when the service session    is established.-   DSL_Line_ID: Subscriber's line identification.-   SP_ID: Identifier of service provider requesting for service.-   Session_Classifier: PPP session classifier used to identify PPP    session traffic flow.-   Session_Priority: Session priority indicator setting to replace the    current one.-   Session_Bandwidth: Session bandwidth information for replacing the    existing one.    4. ChangeSessionBandwidthResponse (DSL_Line_ID, Return_Code)

This message is sent from the Regional/Access Network to the serviceprovider as a response for the bandwidth change request. A Return_Codeis sent back indicating whether the change is successful.

-   DSL_Line_ID: Subscriber's line identification.-   Return_Code: Return code from the Regional/Access Network,    indicating if the request is accomplished successfully.    5. QuerySessionBandwidthRequest (Authorization, DSL_Line_ID, SP_ID)

A NSP can send this message to the Regional/Access Network as a requestfor querying the PPP session bandwidth and priority informationassociated with the specified DSL_Line_ID. The data is stored in the NSPPPP Session Record defined in the DSL Data Model.

-   Authorization: Authorization code obtained when the service session    is established.-   DSL_Line_ID: Subscriber's line ID.-   SP_ID: Identifier of the service provider requesting for bandwidth    and priority information.    6. QuerySessionBandwidthResponse (DSL_Line_ID, Session_Classifier,    Session_Priority, Session_Bandwidth)

This message is sent from the Regional/Access Network to the serviceprovider as a response for the bandwidth info request. The bandwidthdata record is returned.

-   DSL_Line_ID: Subscriber's line identification.-   Session_Classifier: PPP session classifier used to identify PPP    session traffic flow.-   Session_Priority: Current Priority queue setting.-   Session_Bandwidth: Current session bandwidth setting.    7. TerminateServiceSessionRequest (SP_ID, Authorization)

This message is sent from an NSP to the Regional/Access Network as arequest for terminating a communication session.

-   SP_ID: Service Provider Identification.-   Authorization: Authorization code indicating what Regional/Access    Network resources is authorized for the service provider to access.    8. TerminateServiceSessionResponse (SP_ID, Return_Code)

This message is sent from the Regional/Access Network to the serviceprovider as a response for the communication session terminationrequest.

-   SP_ID: Service Provider Identification.-   Return_Code: Return code from the Regional/Access Network,    indicating if the request is accomplished successfully.

6.4 Application Framework Infrastructure

An Application Framework Infrastructure, in accordance with someembodiments of the present invention, is illustrated in FIG. 13 and is areference implementation model for enabling the ASP, NSP, and/orPersonal NSP to utilize the bandwidth and QoS management capabilities.This framework infrastructure is supported by seven functional elements,including ANI Protocol Handler, NNI Protocol Handler, UNI ProtocolHandler, DSL Service Manager, DSL Session Data Store, ProvisionInterface, and BRAS Adapter, in accordance with some embodiments of thepresent invention. For realizing the DSL network bandwidth and QoSmanagement capabilities, this infrastructure may interact with theRouting Gateway via an Automated Configuration Server (ACS) and the BRASto set appropriate policies upon receiving a request from the ASP, NSP,or PNSP, as depicted in FIG. 13.

The communication interface between the Regional/Access Network and anASP is defined as the Application-to-Network Interface (ANI). Thecommunication interface between the Regional/Access Network and a NSP orPNSP is defined as the Network-to-Network Interface (NNI) as discussedabove with respect to the Regional/Access Interface. Through thisframework infrastructure, the ASP, NSP, and/or PNSP can use the DSLNetwork bandwidth and QoS management capabilities to create theirbandwidth and QoS “aware” applications. To enable the communication andservice creation, a DSL Service API may be defined as a part of theRegional/Access Application Framework Infrastructure. This API may be areference procedural implementation of the ANI and NNI.

Any suitable communication interface between the application frameworkand the BRAS and ACS may be utilized and, therefore, will not bediscussed in detail herein. An interface may be used at these points andmay be defined as part of the network element requirements. The use ofCommon Open Policy Service (COPS) is an example standard interface thatmay be implemented at these points to push changes into the ACS andBRAS.

-   -   6.4.1 Framework Infrastructure Element Functional Description

This section describes the main functions of each element of theApplication Framework Infrastructure as illustrated in FIG. 13, inaccordance with some embodiments of the present invention.

ANI Protocol Handler

The ANI Protocol Handler takes a request message from the ASPapplication, passes the request to the DSL Service Manager, waits forthe response from the DSL Service Manager, and sends the responsemessage back to the ASP that requests the service. The protocol used inthis prototype is the Application-to-Network Interface defined in thisproposal.

NNI Protocol Handler

The NNI Protocol Handler takes a request message from the NSP/PNSPapplication, passes the request to the DSL Service Manager, waits forthe response from the DSL Service Manager, and sends the responsemessage back to the NSP/PNSP that requests the service. The protocolused in this prototype is the Network-to-Network Interface defined inthis proposal.

UNI Protocol Handler

The UNI Protocol Handler passes the bandwidth and QoS related parametersvia the ACS to a Routing Gateway associated with a subscriber. Becausethe Routing Gateway obtains its provisioning parameters from the ACSwith a soon to be industry standard interface (WAN-Side DSLConfiguration specification), this same interface may be used tocommunicate bandwidth and QoS information to the RG.

DSL Service Manager

The DSL Service Manager behaves as a service broker that provides one ormore of the following functions: allows ASP/NSP/PNSP to set and querybandwidth and QoS data associated with a PPP session, and to create,change, and delete application flow control record associated with eachindividual application; interacts with BRAS to pass bandwidth and QoSrelated data and policies for prioritizing, shaping, and policingsubscriber's traffic flow either associated with a PPP session or anindividual application flow; and/or communicates with ACS to passbandwidth and QoS related data and polices to a specified Routinggateway working together with BRAS for prioritizing, shaping, andpolicing the subscriber's traffic flow at the access network.

DSL Session Data Store

This is the Master Database maintaining the DSL data model described insection 4.3. It stores all the bandwidth and QoS related data andpolicies that can be queried, modified, created, and deleted by theASP/NSP/PNSP through the ANI/NNI interface. The following records aremaintained in the DSL Session Data Store in accordance with someembodiments of the present invention: a DSL Line Record; an NSP PPPSession Record; a Personal NSP PPP Session Record; an ASP PPP SessionRecord; and/or an application Flow Control Record.

This master copy is replicated in the BRAS and ACS network elements withappropriate data records. The BRAS copy of the data may include thefollowing records in accordance with some embodiments of the presentinvention: an NSP PPP Session Record; a personal NSP PPP Session Record;an ASP PPP Session Record; and/or an Application Flow Control Record.

The ACS network element may include a replica of the following recordsin accordance with some embodiments of the present invention: an NSP PPPSession Record; a personal NSP PPP Session Record; an ASP PPP SessionRecord; and/or an Application Flow Control Record.

DSL Service API

This service creation API is used by the ASP/NSP for creating theirbandwidth and QoS “aware” applications. This API directly maps theANI/NNI protocol defined in this proposal into procedures, methods,and/or other software embodiments, for example, to facilitateapplication programming.

Provisioning Interface

This is a GUI based interface to allow the DSL Service Provider toprovision the bandwidth and QoS settings for each individual subscriberbased on subscriber telephone number, and provision the ASP/NSP thathave a business arrangement with the DSL service provider. The datamodel for support of the provisioning has been defined herein.

-   -   6.4.2 DSL Service Messaging Flow

This section provides several service scenarios to demonstrate how themessaging interface may be used by an ASP application in accordance withsome embodiments of the present invention.

Service Provider Authentication Scenario Messaging Flow

FIG. 14 illustrates the messaging flow for the applicationauthentication scenario in accordance with some embodiments of thepresent invention.

(1) EstablishServiceSessionRequest (SP_ID, SP_Credentials)

This message is sent from the ASP/NSP to the DSLNetwork as a request forestablishing a communication session. The ASP/NSP needs to beauthenticated by the Regional/Access Network before any network servicecan be provided.

Processing Steps:

-   a) ANI/NNI Protocol Handler receives the request message and passes    the request to DSL Service Manager-   b) DSL Service Manager finds the corresponding Service Provider    Record by querying DSL Session Data Store based on the SP_ID-   c) DSL Service Manager validates the SP_Credentials. A result of    authentication is sent back to the ASP/NSP via ANI/NNI Protocol    Handler.

If the authentication is passed, a valid Authorization code is sentback. Otherwise, an invalid Authorization code is returned.

(2) EstablishServiceSessionResponse (Authorization, Return_Code)

This message is sent from Regional/Access Network to ASP/NSP as aresponse for the service session establishment request.

(3) TerminateServiceSessionRequest (SP_ID, Authorization)

This message is sent from the ASP/NSP to the DSL Network as a requestfor terminating the communication session.

-   a) ANI/NNI Protocol Handler receives the request message and passes    the request to DSL Service Manager.-   b) DSL Service Manager finds the corresponding communication    session, terminates the session, and release all the session related    resources.-   c) DSL Service manager sends a result back to the ASP/NSP via    ANI/NNI Protocol Handler.    (4) TerminateServiceSessionResponse (SP_ID, Return_Code)    This message is sent from Regional/Access Network to ASP/NSP as a    response for the service session termination request.    Application Level Bandwidth and QoS Query Scenario Messaging Flow

FIG. 15 illustrates the messaging flow for the application levelbandwidth and QoS query scenario in accordance with some embodiments ofthe present invention.

(1) QueryAppFlowControlRequest (Authorization, DSL_Line_ID, SP_ID,Flow_Classifer)

This message is sent from the ASP to the DSLNetwork as a request forinquiring the bandwidth and QoS information associated with thespecified DSL line.

Processing Steps:

-   a) ANI Protocol Handler receives the request message and passes the    request to DSL Service Manager-   b) DSL Service Manager finds the corresponding DSL Line Record, ASP    PPP Session Record, and Application Flow Record(s) to collect the    requested information.-   c) DSL Service Manager sends the collected bandwidth and QoS info    back to the ASP via ANI Protocol Handler.    (2) QueryAppFlowControlResponse (DSL_Line_ID, Flow_Classifier,    Flow_Priority, Flow_Bandwidth, Return_Code)

This message is sent from Regional/Access Network to ASP as a responsefor inquiring the bandwidth and QoS info request.

Application Level Bandwidth and QoS Modification Scenario Messaging Flow

FIG. 16 illustrates the messaging flow for the application levelbandwidth and QoS query modification scenario in accordance with someembodiments of the present invention.

(1) ChangeAppFlowControlRequest (Authorization, DSL_Line_ID, SP_ID,Flow_Classifier, Flow_Priority, Flow_Bandwidth)

This message is sent from the ASP to the Regional/Access Network as arequest for changing the bandwidth and QoS data associated with thespecified DSL line.

Processing Steps:

-   a) ANI Protocol Handler receives the request message and passes the    request to DSL Service Manager-   b) DSL Service Manager validates the authorization code based on    corresponding Service Provider record, finds the corresponding DSL    Line Record, ASP PPP Session Record, and Application Flow Record(s)    to set the bandwidth and QoS data as requested by the ASP.-   c) DSL Service Manager communicates with BRAS Adapter for passing    related bandwidth and QoS data to BRAS.-   d) BRAS Adapter communicates with BRAS for setting the data in BRAS    own data repository.-   e) DSL Service Manager notifies RG (via ACS) of new bandwidth and    QoS info becoming available by sending the message of    -   UpdateAppFlowControlInfo(DSL_Line_ID, SP_ID, Flow_Classifier,        Flow_Priority, Flow_Bandwidth) through UNI Protocol Handler.-   f) UNI Protocol Handler passes the new bandwidth and QoS data to a    specified RG via ACS.-   g) ACS sends a response message back to UNI Protocol Handler to    confirm the data is received.-   h) UNI Protocol Handler sends the message    -   UpdateAppFlowControlAck(DSL_Line_ID, SP_ID) back to DSL Service        Manager as a response.-   i) DSL Service Manager sends the response message back to ASP via    ANI Protocol Handler.-   j) ACS notifies the specified RG of the availability of new    bandwidth/QoS data via WAN-Side DSL Config Interface.-   k) The specified RG receives notification and downloads the new data    from ACS.    (2) ChangeAppFlowControlResponse (DSL_Line_ID, Return_Code)

This message is sent from Regional/Access Network to ASP as a responsefor setting the bandwidth and QoS request.

Application Flow Control Record Creation Scenario Messaging Flow

FIG. 17 illustrates the messaging flow for the application flow controlrecord creation scenario in accordance with some embodiments of thepresent invention.

(1) CreateAppFlowControlRequest (Authorization, DSL_Line_ID, SP_ID,Flow_Classifier, Flow_Priority, Flow_Bandwidth)

This message is sent from the ASP to the Regional/Access Network as arequest for creating an Application Flow Control Record for a specifiedsubscriber.

Processing Steps:

-   a) ANI Protocol Handler receives the request message and passes the    request to DSL Service Manager-   b) DSL Service Manager validates the authorization code based on    corresponding Service Provider record, finds the corresponding DSL    Line Record, ASP PPP Session Record, and then creates and sets an    Application Flow Control Record as requested by the ASP.-   c) DSL Service Manager communicates with BRAS Adapter for passing    related bandwidth and QoS data to BRAS.-   d) BRAS Adapter communicates with BRAS for setting the data in BRAS    own data repository.-   e) DSL Service Manager notifies RG of new bandwidth and QoS becoming    available by sending the message of    UpdateAppFlowControlInfo(DSL_Line_ID, SP_ID, Flow_Classifier,    Flow_Priority, Flow_Bandwidth) via UNI Protocol Handler.-   f) UNI Protocol Handler passes the new bandwidth and QoS data to a    specified RG via ACS.-   g) ACS sends a response message back to UNI Protocol Handler to    confirm the data is received.-   h) UNI Protocol Handler sends the message    -   UpdateAppFlowControlAck(DSL_Line_ID, SP_ID) back to DSL Service        Manager as a response.-   i) DSL Service Manager sends the response message back to ASP via    ANI Protocol Handler.-   j) ACS notifies the specified RG of the availability of new    bandwidth/QoS data via WAN-Side DSL Config Interface.-   k) The specified RG receives notification and downloads the new data    from ACS.    (2) CreateAppFlowControlResponse (DSL_Line_ID, Return_Code)

This message is sent from DSL Network to ASP as a response for creatingthe application flow control record request.

Application Flow Control Record Deletion Scenario Messaging Flow

FIG. 18 illustrates the messaging flow for the application flow controlrecord deletion scenario in accordance with some embodiments of thepresent invention.

(1) DeleteAppFlowControlRecordRequest (Authorization, DSL_Line_ID,SP_ID, Flow_Classifier)

This message is sent from the ASP to the DSLNetwork as a request fordeleting an Application Flow Control Record for a specified application.

Processing Steps:

-   a) ANI Protocol Handler receives the request message and passes the    request to DSL Service Manager-   b) DSL Service Manager finds the corresponding DSL Line Record and    associated the ASP PPP Session Record. Delete the App Flow Control    Record based on the Flow_Classifier.-   c) DSL Service Manager sends a response back to ASP as a    confirmation.    (2) DeleteAppFlowControlRecordResponse (DSL_Line_ID, Return_Code)

This message is sent from Regional/Access Network to ASP as a responsefor deletion of App Flow Control Record request.

NSP PPP Session Level Bandwidth and QoS Modification Scenario MessagingFlow

FIG. 19 illustrates the messaging flow for the PPP session levelbandwidth and QoS modification scenario in accordance with someembodiments of the present invention.

(1) ChangeSessionBandwidthRequest (Authorization, DSL_Line_ID, SP_ID,Session_Classifier, Session_Priority, Session_Bandwidth)

This message is sent from the NSP to the Regional/Access Network as arequest for changing the PPP session level of bandwidth and QoS dataassociated with the specified DSL line.

Processing Steps:

-   a) NNI Protocol Handler receives the request message and passes the    request to DSL Service Manager-   b) DSL Service Manager validates the authorization code based on the    corresponding Service Provider record, finds the corresponding DSL    Line Record, and the NSP/PNSP PPP Session Record to set the    bandwidth and QoS data as requested by the NSP.-   c) DSL Service Manager communicates with BRAS Adapter for passing    the bandwidth and QoS data to BRAS.-   d) BRAS Adapter communicates with BRAS for setting the data in BRAS    own data repository.-   e) DSL Service Manager notifies RG of new bandwidth and QoS being    available by sending a notification to NNI Protocol Handler.-   f) NNI Protocol Handler passes the new bandwidth and QoS data    associated with a specified RG to ACS by sending the following    message to ACS. UpdateSessionBandwidthinfo(DSL_Line_ID, SP_ID,    Session_Classifier, Session_Priority, Session_Bandwidth).-   g) ACS sends a response message back to NNI Protocol Handler to    confirm the data is received by sending the following message.    -   UpdateSessionBandwidthAck(DSL_Line_ID, SP_ID)-   h) UNI Protocol Handler passes the acknowledgement back to DSL    Service Manager as a response.-   i) DSL Service Manager sends the following response message back to    NSP via NNI Protocol Handler.    -   ChangeSessionBandwidthResponse(DSL_Line_ID, Return_Code)-   j) ACS notifies the specified RG of the availability of new    bandwidth/QoS data via WAN-Side DSL Config Interface.-   k) The specified RG receives notification and downloads the new    bandwidth and QoS data from ACS.    (2) ChangeSessionBandwidthResponse (DSL_Line_ID, Return_Code)

This message is sent from Regional/Access Network to NSP as a responsefor changing the PPP level of the bandwidth and QoS request.

ASP/PPP Session Level Bandwidth and QoS Query Scenario Messaging Flow

FIG. 20 illustrates the messaging flow for the PPP session levelbandwidth and QoS query scenario in accordance with some embodiments ofthe present invention.

(1) QuerySessionBandwidthRequest (Authorization, DSL_Line_ID, SP_ID)

This message is sent from the ASP/NSP to the Regional/Access Network asa request for inquiring the bandwidth and QoS information associatedwith the specified DSL line.

Processing Steps:

-   a) ANI/NNI Protocol Handler receives the request message and passes    the request to DSL Service Manager-   b) DSL Service Manager finds the corresponding DSL Line Record and    the ASP/NSP PPP Session Record to collect the requested information.-   c) DSL Service Manager sends the collected bandwidth and QoS info at    PPP session level back to the ASP/NSP via AN/NNI Protocol Handler.    (2) QuerySessionBandwidthResponse (DSL_Line_ID, Session_Classifier,    Session_Priority, Session_Bandwidth, Return_Code)

This message is sent from Regional/Access Network to ASP/NSP as aresponse for inquiring the bandwidth and QoS info request.

7. Future Capabilities of the Application Framework

Exemplary embodiments of the invention have been described above withrespect to an Application Framework comprising a reference data modeland an interface specification defined for specific transport flowsrelated to QoS and bandwidth capabilities. This Application Frameworkmay be expanded, in accordance with some embodiments of the presentinvention to support other services that link network services,telecommunications information technology, and customers including, forexample: registration—enables the ASP to register services/applicationswith the Regional/Access Network; discovery—enables the Subscriber todiscover services/applications within the Regional/Access Network;subscription—enables the ASP to manage and maintain subscriber accounts;management—for validation of subscribers and relatedservices/applications; session—enables the xSP to manage and maintainsession establishment, Management: session control, and session teardownfor subscriber access to services/applications; authentication—enablesthe xSP to validate the user/subscriber for network access andservices/applications access—who are you?; authorization—enables the xSPto validate the user/subscriber for network access andservices/applications access—what permissions do you have?;profile—enables the xSP to manage and maintain user/subscriber profiledata; identify—enables the xSP to manage and maintain user preferences,profiles, identity data; presence—enables the xSP to know and maintainawareness of the current existence of the subscriber;notification—enables the xSP to notify the subscriber of relatedservices/applications information; and/or billing—enables the xSP tocapture subscriber/user billing data for network usage andservices/applications usage for mediating a common billing record. Theseother capabilities may provide a host of centralized software servicessupporting a distributed network computing environment linkingusers/subscribers to their desired services and applications.

8. Example Use Scenario—Turbo Button

A source of potential frustration for users of data services is thatdata rates supported by the network (e.g., 1.5 Mb/s downstream and 256Kb/s upstream) are often not properly matched with applicationrequirements. Even with the higher speeds afforded with DSL access,users of many applications (e.g., content download such as large MSOffice service packs or movie trailers, and on-line gaming) may beinterested in using a service that would provide an even higher accessspeed at the times they need it most by invoking a “Turbo Button”service. The higher access speed limit is achieved via a service profilechange that eliminates or lessens artificially imposed limits on theachievable speed in the user's PPP session. This section shows how theDSL Application Framework can support such a service, in accordance withsome embodiments of the present invention, starting with the referencemodel shown in FIG. 21.

Many implementations of a Turbo Button service are possible inaccordance with various embodiments of the present invention. For thepurposes of this section, we will work with a fairly simpleimplementation in which the service is provisioned by an NSP calledmyNSP.com. The user requests the turbo button service at the communityNSP's website during a browsing session at normal speed. Note that otherordering mechanisms are possible including mechanisms that are separatefrom the DSL session, e.g., using a telephone or a mass-distributed CD.

As mentioned above in certain embodiments of the present invention, theservice is implemented via provisioning rather than by using real-timesignaling. Under this assumption, a provisioning cycle is initiatedafter the user invokes the service and the provisioning completes beforethe effect is seen. Another result of this assumption is that the effectof the user's service invocation is permanent, i.e., once turbo speed inplace, it lasts until the user cancels the service and anotherprovisioning cycle occurs to reinstate the default service parameters.Real-time signaling may be needed to support a service that supportson-demand, brief turbo sessions on an as needed basis.

Once the user requests the turbo service, the NSP queries theRegional/Access network to find out what turbo options can be presentedto the user. The NSP may map the available upgrades to marketingcategories (e.g., fast, faster, wickedly fast). The user selects one ofthe options, and the NSP requests the profile from the Regional/Accessnetwork that supports the requested speed. The Regional/Access networkin turn pushes new policy (e.g., classifiers, rate limiters, priority)into the user's RG that will support the higher speed. It is importantto note that the service is still “Best Effort,” i.e., there is noassumption of a QoS guarantee at this time. A version of turbo buttonservice with QoS support may be implemented in accordance with otherembodiments of the present invention.

We will assume that the NSP authenticates its own users for servicessuch as Turbo Button. A centralized authentication service (as well asother ancillary services such as billing and presence functionality)could be implemented in the Regional/Access network on behalf of NSPsand ASPs in accordance with additional embodiments of the presentinvention. In a typical business model, the NSP might bill the user forusage of the turbo button service. In turn, the DSL network providerwould bill the NSP for carrying traffic across the Regional/Accessnetwork at turbo speeds.

Turbo Button Scenario Description

FIG. 22 illustrates an example of the sequence of events occurring withusing the Turbo Button Service to access sites via a network serviceprovider called “myNSP.com.” For simplicity of illustration, the detailsof the Regional/Access network (DSL Service Manager, UNI and ANIprotocol handlers, ACS, BRAS, etc.) are not shown—the expanded flowswere shown in Section 6.4. The step numbers shown in the figurecorrespond with the list provided below.

1. The user clicks an advertisement to reach the NSP's Turbo Buttonsubscription menu.

2. The NSP host authenticates itself with the Regional/Access network inorder to be able to access the customer profile it wants to update.

3. Once authenticated, the NSP host then queries the Regional/Accessnetwork for available options for the users access session connection.It uses the response to this query to put together a set of options forpresentation to the customer.

4. The user selects one of the options.

5. The NSP requests the Regional/Access network to change the sessionbandwidth associated with the access session. A notification may be sentto the user indicating that the turbo button provisioning is under wayand that turbo speed will be available later that day (for example).

6. Using Update Session Bandwidth messaging, the Regional/Access networkpushes new policy to the RG that will support the turbo speed.

7. Once the new policy is in place, the user is able to enjoy turbospeed access to sites served by the NSP. Note that all users connectedto the access session (i.e., other PC users on the household LAN) wouldalso enjoy the benefits of the turbo button service.

8. Later, the user decides to cancel turbo button service.

9. Steps 5 and 6 are repeated with the profile and policy put in placebeing those needed for default access session speeds.

10. The network has returned to its previous state and the user's PPPsession is no longer turbo'd.

9. Example Use Scenario—Video Conferencing

This section illustrates how the DSL Application Framework can support avideoconference service in accordance with some embodiments of thepresent invention. The videoconferencing model used is a SIP-drivenservice implemented by an ASP with a centralized control/mixingconference server. This is the tightly coupled model being developed byan IETF Sipping WG design team that uses four logical entities: focus,conference state notification service, conference policy server element,and stream mixers. There are several ways that these entities can bespread over the available network segments. For example, the ASP and theRegional/Access network can each implement a subset of the entities; forexample, the ASP can implement the stream mixing while the rest of thelogical entities are implemented in the Regional/Access network. Such adivision may be feasible from a technical perspective, but theadditional exposed interfaces may require standardization or bilateralagreement. There might not be much of a business case for such a modelbecause there is little incentive for either the ASP or Regional/Accessnetwork to give up part of the service offering.

Furthermore, all of the entities can be implemented in theregional/Access network. This option offers some simplicity from theRegional/Access network provider's perspective because no ASP isinvolved. This would probably balanced, however, by the networkprovider's need to decouple the videoconference service offering fromthe general DSL networking aspects.

Finally, the ASP can implement all of the logical entities while theRegional/Access network provider concentrates on the transport issues.This approach is adopted for the rest of this section—the ASP handlesall of the mixing as well as the application layer control. A referencediagram for the service with three users is shown in FIG. 23.

From the user's perspective, the videoconferencing service has thefollowing capabilities in accordance with some embodiments of thepresent invention: Creation/Activation: the user can interact with theASP and either request a reserved conference (without pre-designatedparticipants) or activate a previously reserved conference; Termination:the conference ends at a pre-designated time; Adding Participants: Allusers are designated in advance; Dropping Parties: Although individualparties may stop participation in the conference, the resources in thenetwork supporting their connections remain in place; and/or StreamMixing: Basic audio and video mixing are provided. Each participantreceives all of the other participants' audio and receives video fromthe participant with the loudest current audio.

Assumptions regarding the service are as follows: the ASP that offersthe videoconference service will host the MCU; the ASP's MCU willsupport the ASP's subscribers in all ASP networks for which that ASP isparticipating; videoconference client software compatible with an ASP'svideoconference service is resident on all participant PCs; users thatare not subscribed to the ASP's videoconference service will not besupported; DHCP leases do not expire; SIP Application Level Gateway(ALG) functions for handling NAT traversal are provided in the RG; theASP providing the videoconference service maintains a common addressrepository or locator for its subscribers. ASP's may be unwilling toshare or store their subscriber information in a network database;mechanisms are in place to support application level communicationbetween two ASP networks (see the dotted line shown); the ALG functionsin the RG use DiffServ Code Points (DSCP) from the voice and videostreams and the port information pushed to it through the ACS profile tomap audio and video flows to ports that are known to the BRAS forreclassification. A simpler approach may be to classify packets comingfrom the videoconference client based on packet type and protocol ID butthat would mean the audio and video RTP streams could not bedistinguished by the classifier and would have to share the samepriority; the DSCPs used by the videoconference clients arestandardized; and/or by its nature RTP is a unidirectional stream, butRTCP is bi-directional. Each pair of RTP and RTCP UDP streams defines achannel. To simplify the presentation, only one direction of the RTPstream is shown for audio and data and only one control stream is shown.Typical SIP and H.323 videoconference implementations may requireadditional data and control streams to complete fully bi-directionaldata flows for all participants.

At least two workable business models can support this videoconferencingservice. In the simplest model, the videoconference ASP arranges for allpotential conference participants to have the necessary policies inplace to support the service. Once this infrastructure is provisioned,any subset of the participants can hold a videoconference at any time. Aslightly more complex model has some advantages for demonstrationpurposes—in this model, the videoconference ASP makes the necessarychanges needed in the network to support a particular videoconference(and only the participants for that conference receive upgraded profilesto support their session). This model, which is used in this section,does not require that the policy be in place at all times, but mayrequire a window (perhaps 24 hours) during which the provisioningchanges are made.

A number of billing models are possible. In some embodiments, the ASPbills (flat rate, usage, etc.) videoconference subscribers for theirservice. The Regional/Access network provider bills the ASP for hostingthe service on the ASP network and for the usage of the Regional/Accessnetwork. Note that additional opportunities for the business model arepossible for offering centralized billing, authentication, and presencecapabilities to videoconference ASPs.

The static provisioning model imposes some restrictions onvideoconferencing service models. Reservations are made well in advanceto allow the flow-through provisioning to occur before the start of theconference. The reservation window thus needs to close before the startof the conference, for example 24 hours prior. No real-time adjustmentof the schedule (such as early teardown because the participantsfinished early) is possible. The only way to update the participant listis for the user to request a replacement conference before thereservation window closes.

Despite the use of the static provisioning model, the ability to map aparticular conference's flows to a classifier still makes it possible tooffer reasonable service features. The user may be able to set upmultiple conference calls with different sets of people and withdifferent QoS and bandwidth requirements (for example, a reduced framerate may be desired for a conference a day after the conference in thisexample because several BRI users will be on the call). Without themapping between the flows and the classifier, the user may have beenable to have only one outstanding conference request. In addition, theuser may be able to modify the arrangements for a particular conference(e.g., if the participant roster or start/end times change) providedthat the reservation window (24 hour notice) has not closed.

A goal of this section is to demonstrate that the Framework andInterface and Data Model are sufficient to support this basicvideoconference service. After discussing the individual streams neededfor videoconferencing, flows for setting up and tearing downvideoconferencing flows in accordance with some embodiments of thepresent invention are presented. At the end of this section, the networkmodel is expanded to include the DSL network's entities and furtherexercise the data model and messages that have been defined.

Videoconferencing Scenario Descriptions

The following sequence of events may occur in the process of registeringfor the ASP videoconference service, reserving a particular conference,and tearing it down once the conference is over. Assume that three usersA, B, and C will be involved in the videoconference and that A will bethe originator. For simplicity, the details of the Regional/Accessnetwork (DSL Service Manager, UNI and ANI protocol handlers, ACS, BRAS,etc.) are not shown—the expanded flows have been shown in Section 6.4.The step numbers shown in FIGS. 24 and 25 correspond with the listprovided below:

-   -   1. Assume that Users A, B, and C already have established PPP        sessions between their RG's and the DSL network provider.    -   2. On the videoconference ASP website, User A registers to be        able to set up videoconferences by setting up their user        profile, billing options, etc.    -   3. User A decides to hold a videoconference with Users B and C        on Tuesday 3:00-4:00 and arranges this with the videoconference        ASP.    -   4. The ASP establishes a service sessions with the        Regional/Access network and is authenticated.    -   5. The ASP sends application flow control requests to the        Regional/Access network requesting changes to support the        videoconference.    -   6. The Regional/Access network pushes new application flow        policies to the BRAS, ACS, and RG's A, B, and C that are        specific to the videoconference application. The videoconference        stream facilities are now available.    -   7. The videoconference starts at 3:00 on Tuesday (note that the        flow has now moved). Inside the control streams, the        videoconference ASP uses SIP to establish the necessary        conference legs to users A, B, and C. The streams from the users        are placed appropriately in the queues by the classifiers, are        mixed by the videoconference ASP, and appropriately mixed        streams are distributed to the participants.    -   8. At 4:00 on Tuesday, the conference is scheduled to end. The        videoconference ASP releases its internal resources for the        mixers and conference control, sends SIP BYE messages through        the control stream to clear the SIP dialogs with the users, and        sends a billing record so that the appropriate charging takes        place.    -   9. The videoconference ASP establishes a service session with        the DSL network (if necessary) and is authenticated.    -   10. The videoconference ASP requests deletion of the application        flow control records that supported the videoconference.        The Regional/Access network deletes the policy for the bandwidth        and QoS at the BRAS, ACS, and RG's for users A, B, and C. The        network has now been returned to its default state.        Flow Classification for Video Conferencing

The videoconference service may require three streams to carry audio,video, and signaling/control as shown in FIGS. 24-27. The flows referredto using a “+” sign in FIG. 27 may be set up dynamically at the VCclient and the DSCP may be assigned for the audio and video streams. TheALG/NAT maps of the 10.X.X.X ports to the corresponding IP address andports for audio and video specified in the ACS profile based on the DSCPset by the VC client. This may ensure that the RG, BRAS and ASPvideoconference MCU maintain consistent port information with regard tothe various flows.

The signaling/control stream is used at the application layer forpurposes, such as floor control and other needs, that are transparent tothe Regional/Access network provider. Assume that audio and controlpackets need to travel with high priority and thus are placed into theExpedited Forwarding queue at the RG. Video packets have medium priorityand hence will be placed into the Assured Forwarding queue at the RG.The videoconference service does not cause the user to emit any lowpriority packets that we are aware of; thus, the RG will not need toplace any packets into the Best Effort queue.

A goal is to demonstrate that it is possible for the ASP to push packetclassifier information into the DSL network at conference reservationtime so as to configure the DSL network for proper placement of packetsfrom the three streams into the appropriate queues as mentioned above.At the time that a videoconference is reserved (to occur in this case3:00-4:00 the next day), the user needs to get a conferenceidentifier/PIN from the videoconference ASP. The user will use thisconference identifier to get into the correct conference the next day,and will give the conference id to the other participants for the samepurpose. For the purposes of this section, assume that this conferenceidentifier does not need to show up in the data model because it isstrictly between the users and the ASP and somehow transferredtransparently to the DSL network provider.

The ASP needs to set up bandwidth and priority for the three streams(control, video, and audio) that are needed between each user and theASP using a Create Application Flow Control Request message. One benefitof looking at videoconference as a service example is to betterunderstand how the various flows would be set up and managed throughNATs and firewalls and still have those flows appropriately classifiedthroughout. Many protocols establish connections on well-known portsthat spawn data flows on ephemeral ports (i.e., dynamically spawned andassigned to a given multimedia call after the initial handshakes). Theproblem of firewall and NAT traversal is a complex one due, in part, tothe large number of different scenarios and the multitude of differentsolutions to solve them.

For this example, it is assumed that the RG has an ALG function for thesupport of SIP. Further it is assumed that there is a “trusted”relationship between the ASP and the Regional/Access network and the useof DSCP markings of packets can be used as part of the classificationprocess.

Referring to FIG. 24, information that is used for setting up andclassifying the flows required for a videoconference in accordance withsome embodiments of the present invention is illustrated. First, duringthe initial setup, user A registers all participants and specifies thestart time and end times, etc.. The ASP reserves IP addresses for theconference on its platform and updates each participant's RG by issuinga createAppFlowReq request to the Regional access network. The BRAS usesthe IP addresses specified by ASP, for reclassifying traffic to ASP, andwill use the IP of the RG and the DSCP for reclassifying traffic enroute to the videoconference client. The profile that gets pushed toeach participant will contain ASPi's IP addresses for control, audio,and video flows. When the start time for the videoconference approaches,each participant will activate their videoconference client on his orher PC and login to the reserved conference.

Once ASP, receives the control message for call setup, it can refer toits table of reserved addresses to be used for the conference.Capability set negotiation occurs at this time (e.g., could be includedin SDP component). The RG's ALG/NAT engine uses the DSCP and informationfrom the ACS profile to determine which port it should assign to the RTPflows from the videoconference client. This may ensure consistency forthe port information stored in the BRAS for reclassification. ASPI, theBRAS, and the RG should now know all addresses, priorities and shapinginformation. The videoconference client's RTP streams can begin pushingaudio and video.

10. Example Use Scenario—Gaming

This section illustrates how the DSL Application Framework can support agaming service in accordance with some embodiments of the presentinvention. Though there are many different models for game play anddelivery, this section discusses a particular class of games known as“massively multi-player interactive” games. Such games are characterizedby substantial numbers of players (greater than 10 and up to the 1000s)and real time or near real-time interactions. Such games placesignificant demands on network and game server infrastructures. Otherclasses of games that are not discussed here include turn based games,single player (turn based or real time interactive), and head to headinteractive games. Though each of these classes represents a significantnumber of games available to users, their network requirements are notnearly as complex as those of multi-player interactive games.

Gaming Service Overview

Two basic topologies are used to support network gaming: point to pointor client server. In client server topology, the player's workstationcommunicates with a central game server to which other players are alsoconnected. In the point to point topology, each player communicatesdirectly with each other player. A refinement of the client servertopology, the hierarchical client server topology, provides thenecessary infrastructure to support true massively multi-playerenvironments. These topologies are depicted in FIG. 28.

In the point to point topology, each gaming workstation must transmitits moves and state change information to each other gaming workstation.In addition, each workstation must maintain a consistent andsynchronized image of the game universe for each player. As such thepoint to point topology requires significant computation power in theend user workstation and typically will not scale to supporting morethan a number of users.

In both forms of the client server topology, the workstation and gameserver exchange information that is directly relevant only to a specificplayer. The client workstation is responsible for such tasks as managinguser interactions, rendering, and audio feedback, while the server isresponsible for maintaining a consistent view of the game universe andcommunicating changes to the view to player workstations. The differencebetween the two topologies is one of segmentation. In the hierarchicaltopology, a server is only responsible for maintaining the state of aportion of the universe. If a player connected to a particular server isinteracting with a portion of the universe outside the scope of theirimmediate server, that server must coordinate with other servers in thenetwork. This partitioning provides significantly more scalability thana simple client server topology.

In addition to maintaining game universe state at communicating statechanges to players, a gaming service may provide other auxiliaryfunctions including the following: Session Management: manages activeplayer lists, supports ability to invite participants to join a game;presence and availability management: supports the ability of players tolocate and determine if opponents are available for play;authentication: verify player identities and validate that players areusing correctly licensed software on their workstation; interactive chatand bulletin board: provides a forum for discussion of gaming topics.Can also be used during game play to allow for intra-team communication;and/or content downloads: provides software update and new game deliveryservices.

Basic game server functionality and auxiliary functions represent agaming service that may be offered in an ASP model in accordance withsome embodiments of the present invention. The game server and serversfor auxiliary functions are connected to the ASP network. Clientworkstations access a game server or auxiliary function server throughtheir ASP network connection. From the perspective of the DSL network,whether a gaming service implements a client/server or hierarchicalclient/server topology is not important. The DSL network is onlyinvolved in the transport of traffic between one or more gameworkstations and the game server to which they are connected. Thisservice model is show in FIG. 29.

Traffic and Flow Characterization

In a client/server multiplayer gaming service, the game server andplayer workstation communicate state change and play event informationin real time. The workstation informs the server of player triggeredevents including the following: Player moves; Player takes a shot;Player changes rooms; and/or Player picks up an object.

In a real-time game, the server reconciles these play event messages asthey are received from each workstation or peer server. It thencommunicates state change information to each client workstation. Thesestate change messages contain only information relevant to theparticular player—only information about objects currently visible tothe player is communicated. Examples of this information include:movement of other objects within the player's current view; hits made bythe player; damage incurred by the player; death of the player or otherplayers; and/or communication from the server or other players.Unfortunately, there does not appear to be a standard protocol for suchcommunications; each gaming system seems to define its own methods ofcommunication. The basic characteristics, however, seem to be similar.

While communication from the workstation to the server is typicallyevent driven, server to workstation communication is often continuous.Servers often send state change messages in frames at a defined rate—10,20, 30 frames per second. Frames tend to be significantly larger thanvoice or video frames. The total time required to send a user event,reconcile its impact on the game universe, and communicate state changeback to the workstation may become the limiting factor in playerreaction time. The longer the total time, the less reactive a player canbe and the less interactive the gaming experience may become.

Reconciliation time is driven by server capacity and load. Messagedelivery times are driven by network limitations. For many games, atotal round trip “ping” time of 200-350 ms is considered acceptablewhile 100 ms is considered exceptional. Anything greater than 500 ms maybecome very obvious to the player and is perceived as sluggishness. Aslatency increases it becomes more likely that players do not share aconsistent view of the universe.

In summary, game play related traffic can be characterized as follows:steady frame rate; large frame size (relative to voice or video); and/orlatency sensitive Auxiliary services generally do not share thesecharacteristics. They typically are similar or identical to traditionalInternet Web based services and do not suffer from significant impactsdue to latency.

The bandwidth requirement for play related traffic is generally lowerthan for video services, but the latency sensitivity of game playtraffic typically necessitates better than best-effort treatment. Flowsrelated to game play may be placed in an assured forwarding queue at aminimum. Auxiliary services may be handled on a best effort basis. Playrelated traffic and auxiliary service traffic are typically carried indifferent flows.

Traffic within a game play flow may be further differentiated inaccordance with additional embodiments of the present invention. Forexample, within the context of a particular game certain events may betreated with higher priority than others. This may be supported byallowing the application to use and set multiple diffserv code-points.Such use, however, may only be permitted if there is a trustedrelationship between the ASP gaming host and the transport network.

Example Scenario Description

The call flow for gaming is similar to Turbo button. The game providerneeds to negotiate bandwidth profiles between the game server and theplayer workstation for the purposes of game play traffic. The steps inthis scenario are illustrated in FIGS. 30 and 31, in accordance withsome embodiments of the invention, as follows:

-   -   1. Subscriber establishes PPP session between RG and DSL network        provider.    -   2. Subscriber accesses ASP gaming providers web site and        registers for game play.    -   3. ASP gaming provider queries subscriber bandwidth profile and        determines current profile to be insufficient for game play.    -   4. ASP creates application bandwidth/QOS profile at Regional        Access Network.    -   5. ASP acknowledges subscription.    -   6. Regional access network pushes new flow qualifier and        bandwidth info for game service to routing gateway.    -   7. Subscriber joins game using QOS enabled session.        11. Modifying Bandwidth and/or QoS in a Core Network

Methods, systems, and/or computer program products for modifyingbandwidth and/or QoS in a Regional/Access Network (RAN) that comprises acore network, according to some embodiments of the present invention,will now be described. The RAN facilitates differentiated end-to-enddata transport between a Network Service Provider (NSP) and/or anApplication Service Provider (ASP) and a Customer Premises Network (CPN)according to some embodiments of the present invention. The RAN, NSP,ASP, CPN, and RG have been described extensively above and thisdescription will not be repeated in the interest of brevity. Moreover,some messages that are referenced in this section are described indetail in Section 6. Moreover, the RAN may include the elementsillustrated in FIGS. 3-5 along with a core network that includes, forexample, routing elements, in accordance with some embodiments of thepresent invention. For example, a core network elements in a RAN mayinclude a plurality of policy enabled routers in accordance with someembodiments of the present invention. Core network elements in a RAN mayalso include a plurality of multiprotocol label switching (MPLS) routersthat support traffic engineering.

Various embodiments of a DSL Application Framework Infrastructure,illustrated, for example, in FIG. 13, have been described above withrespect to managing bandwidth and/or QoS in the access network.Historically, core network resources are assumed to be trafficengineered in a relatively static fashion. Often this is because coreresource changes involve changes to facilities. Embodiments of thepresent invention stem from a realization that bandwidth and/or QoS maybe modified in the core network and/or the edge network in a dynamicfashion without a need to reconfigure hardware facilities assuming, forexample, that the facilities are not already provisioned at theirmaximum capacities should a request be made for increased bandwidth. Forexample, an enterprise may want to dynamically increase the bandwidth ofthe resources allocated to it in the core network and/or the edgenetwork to perform a centralized backup of data from the enterprise'sremote sites. As another example, an ASP may anticipate a large surge incustomer demand and may want to increase the bandwidth of the resourcesallocated to it in the core network and/or the edge network to servicethis increased demand.

Referring now to FIG. 32, a framework infrastructure for managingbandwidth and/or QoS in a core and/or edge network 3200 may be embodiedin a RAN node, such as, for example, the BRAS, a policy enabled router,and/or a multiprotocol label switching (MPLS) router that supportstraffic engineering. Moreover, the framework infrastructure 3200 may beused in addition to or in place of the DSL application frameworkinfrastructure illustrated in FIG. 13. The framework infrastructure 3200comprises a network resource service manager 3210 that iscommunicatively coupled to NSPs, ASPs, and/or enterprises 3220 via anAPI interface 3230. The network resource service manager 3210 may alsobe communicatively coupled to a core network 3240 via a core networkinterface module 3250. The core network 3240 may have interfaces withone or more edge networks of similar or dissimilar types. In otherembodiments, the network resource service manager 3210 may becommunicatively coupled to an Operational Support System (OSS) 3260 thatmanages the core network 3240. An information repository 3270, such as adatabase, may be used to store the topology of core network resourcesallocated to various NSPs, ASPs, and/or enterprises. The informationrepository 3270 may be accessed via the network resource service manager3210 and via the OSS 3260 via a provisioning interface module 3280. Inaccordance with some embodiments of the present invention, the networkresource service manager 3210 may be configured to process API callsinitiated by NSPs, ASPs, and/or enterprises to query a resourceallocation in the core network 3240 that is assigned to particular NSPs,ASPs, and/or enterprises, and to process API calls initiated by NSPs,ASPs, and/or enterprises to modify the bandwidth and/or the QoS of theresource allocation in the core network 3240 and/or the edge network(s)that is assigned to particular NSPs, ASPs, and/or enterprises.

The API interface 3230 may comprise the Application-to-Network Interface(ANI) defined between the RAN and an ASP and/or the Network-to-NetworkInterface (NNI) defined between the RAN and an NSP. Advantageously, theAPI may allow an NSP and/or ASP to modify bandwidth and/or QoS in thecore network 3240 and/or the edge network(s) regardless of thetechnology used within the RAN.

The present invention is described herein with reference to flowchartand/or block diagram illustrations of methods, systems, and computerprogram products in accordance with exemplary embodiments of theinvention. It will be understood that each block of the flowchart and/orblock diagram illustrations, and combinations of blocks in the flowchartand/or block diagram illustrations, may be implemented by computerprogram instructions and/or hardware operations. These computer programinstructions may be provided to a processor of a general purposecomputer, a special purpose computer, or other programmable dataprocessing apparatus to produce a machine, such that the instructions,which execute via the processor of the computer or other programmabledata processing apparatus, create means for implementing the functionsspecified in the flowchart and/or block diagram block or blocks.

These computer program instructions may also be stored in a computerusable or computer-readable memory that may direct a computer or otherprogrammable data processing apparatus to function in a particularmanner, such that the instructions stored in the computer usable orcomputer-readable memory produce an article of manufacture includinginstructions that implement the function specified in the flowchartand/or block diagram block or blocks.

The computer program instructions may also be loaded onto a computer orother programmable data processing apparatus to cause a series ofoperational steps to be performed on the computer or other programmableapparatus to produce a computer implemented process such that theinstructions that execute on the computer or other programmableapparatus provide steps for implementing the functions specified in theflowchart and/or block diagram block or blocks.

Referring now to FIG. 33, operations for modifying bandwidth and/or QoSin a core network begin at block 3300 where the enterprise, NSP, and/orthe ASP may optionally be authenticated at the RAN. In accordance withparticular embodiments of the present invention, the NSP and/or the ASPmay be authenticated by sending an establish service session requestmessage from the enterprise, NSP, and/or the ASP to the RAN thatcontains an identification of the enterprise, NSP and/or the ASP alongwith authorization credentials. The RAN may send an establish servicesession response message back to the enterprise, NSP and/or the ASP thatcontains an authentication result. The establish service session requestmessage and the establish service session response messages have beendescribed above.

At block 3310, the enterprise, NSP, and/or the ASP uses API calls tocommunicate with the RAN to query a resource allocation in the corenetwork and/or edge network(s) that is assigned to the enterprise, NSP,and/or the ASP. In accordance with various embodiments of the presentinvention, the network resource service manager 3210 of FIG. 32 mayquery the core network 3240 and/or edge network(s) directly or,alternatively, may query the core network 3240 and/or edge network(s)via the OSS 3260. In particular embodiments of the present invention,the enterprise, NSP, and/or ASP may send a query network resourcerequest message to the network resource service manager 3210 via the APIinterface 3230 that contains a request for information on resourceallocation in the core network 3240 and/or edge network(s) that isassigned to the enterprise, NSP, and/or ASP. The query network resourcerequest message may have a format ofQueryNetworkResourceRequest(Authorization, Resource_ID) whereAuthorization is the authorization code obtained when the servicesession is established and the Resource_ID is an identification of thecore and/or edge network resource. A query network resource responsemessage may be sent from the RAN to the enterprise, NSP, and/or ASP thatcontains the information on resource allocation in the core network 3240and/or edge network(s) that is assigned to the enterprise, NSP, and/orASP. The query network resource response message may have a format ofQueryNetworkResourceResponse(Resource_ID, Flow_Classifier,Resource_Priority, Resource_Bandwidth, Return_Code), where Resource_IDis an identification of the core network resource, Flow_Classifier is aclassifier used to identify a traffic flow associated with the coreand/or edge network resource, Resource_Priority is a priority associatedwith the traffic flow associated with the core and/or edge networkresource, Resource_Bandwidth is a bandwidth associated with the coreand/or edge network resource, and Return_Code is a return code thatindicates whether the query was successful.

At block 3320, the enterprise, NSP, and/or the ASP uses API calls tocommunicate with the RAN to modify the bandwidth and/or QoS of theresource allocation in the core network 3240 and/or edge network(s) thatis assigned to the enterprise, NSP, and/or the ASP. In some embodimentsof the present invention, the QoS may be a priority associated with thetraffic flow associated with the core and/or edge network resourcesallocated to the enterprise, NSP, and/or the ASP. In accordance withvarious embodiments of the present invention, the network resourceservice manager 3210 may modify the bandwidth and/or the QoS of theresource allocation in the core network 3240 and/or edge network(s) thatis assigned to the enterprise, NSP, and/or the ASP directly.Alternatively, the resource service manager may communicate with the OSS3260 to modify the bandwidth and/or the QoS of the resource allocationin the core network 3240 and/or edge network(s) that is assigned to theenterprise, NSP, and/or the ASP. In particular embodiments of thepresent invention, the enterprise, NSP, and/or ASP may send a changenetwork resource request message from the enterprise, NSP, and/or ASP tothe RAN that contains a request for changing the bandwidth and/or theQoS (e.g., traffic priority) of the resource allocation in the corenetwork 3240 and/or edge network(s) that is assigned to the enterprise,NSP, and/or ASP. The change network resource request message may have aformat of ChangeNetworkResourceRequest(Authorization, Resource_ID,Resource_Priority, Resource_Bandwidth) where the message fields havebeen described above. A change network resource response message may besent from the RAN to the enterprise, NSP, and/or ASP that contains anacknowledgement for the change network resource request message. Thechange network resource response message may have a format ofChangeNetworkResourceResponse(Resource_ID, Return_Code) where themessage fields have been described above.

Thus, embodiments of the present invention may be used to dynamicallymodify the bandwidth and/or QoS of core and/or edge network resourcesallocated to an enterprise, NSP, and/or ASP. For example, enterprisecustomers may purchase 1 Gig service to access a storage location forbacking up their data. A core bandwidth of 1 Gbps may be sufficient forindividual customers; however, all customers may not be provided with 1Gbps service simultaneously. Thus, the enterprise may use the APIinterface 3230 to the network resource service manager 3210 to reservecore network 3240 resources for various customers at various times. Thismay ensure that each customer has sufficient bandwidth through the corenetwork 3240 when the customer attempts to perform its data backup. Asanother example, an inter-exchange carrier may connect to a core networkat a plurality of points. As the inter-exchange carrier getsmove/add/delete orders from its customers, it may request changes in thecore network 3240 through the API interface 3230 and the networkresource service manager 3210 to obtain the proper bandwidth and QoS forthe aggregation links within the core network that are assigned to theinter-exchange carrier. In this way, the inter-exchange carrier maymanage a virtual access network that physically comprises part of a corenetwork and a conventional access network.

The flowchart of FIG. 33 illustrates the architecture, functionality,and operations of some embodiments of systems, methods, and computerprogram products for modifying bandwidth and/or QoS in a core and/oredge network. In this regard, each block represents a module, segment,or portion of code, which comprises one or more executable instructionsfor implementing the specified logical function(s). It should also benoted that in other implementations, the function(s) noted in the blocksmay occur out of the order noted in FIG. 33. For example, two blocksshown in succession may, in fact, be executed substantially concurrentlyor the blocks may sometimes be executed in the reverse order, dependingon the functionality involved.

Many variations and modifications can be made to the embodimentsdescribed herein without substantially departing from the principles ofthe present invention. All such variations and modifications areintended to be included herein within the scope of the presentinvention, as set forth in the following claims.

1. A method of modifying bandwidth and/or Quality of Service (QoS) in aRegional/Access Network (RAN) that comprises a core network, the RANfacilitating differentiated end-to-end data transport between anenterprise, a Network Service Provider (NSP), and/or an ApplicationService Provider (ASP) and a customer Premises Network (CPN),comprising: using Application Programming Interface (API) calls at theenterprise, NSP, and/or the ASP to communicate with the RAN to query aresource allocation in the core network that is assigned to theenterprise, NSP, and/or the ASP; and using API calls at the enterprise,NSP, and/or the ASP to communicate with the RAN to modify the bandwidthand/or the QoS of the resource allocation in the core network that isassigned to the enterprise, NSP, and/or the ASP.
 2. The method of claim1, further comprising: querying the core network directly from the RANto obtain the resource allocation in the core network that is assignedto the enterprise, NSP, and/or the ASP.
 3. The method of claim 1,further comprising: querying an Operational Support System (OSS)associated with the core network to obtain the resource allocation inthe core network that is assigned to the enterprise, NSP, and/or theASP.
 4. The method of claim 1, further comprising: modifying thebandwidth and/or the QoS of the resource allocation in the core networkthat is assigned to the enterprise, NSP, and/or the ASP directly fromthe RAN.
 5. The method of claim 1, further comprising: communicatingwith an Operational Support System (OSS) to modify the bandwidth and/orthe QoS of the resource allocation in the core network that is assignedto the enterprise, NSP, and/or the ASP.
 6. The method of claim 1,wherein the QoS of the resource allocation in the core network that isassigned to the enterprise, NSP, and/or the ASP is traffic priority. 7.The method of claim 1, wherein using API calls at the enterprise, NSP,and/or the ASP to communicate with the RAN to query the resourceallocation in the core network comprises: sending a query networkresource request message from the enterprise, NSP, and/or the ASP to theRAN that contains a request for information on resource allocation inthe core network that is assigned to the enterprise, NSP, and/or theASP; and sending a query network resource response message from the RANto the enterprise, NSP, and/or the ASP that contains the information onresource allocation in the core network that is assigned to theenterprise, NSP, and/or the ASP.
 8. The method of claim 1, wherein usingAPI calls at the enterprise, NSP, and/or the ASP to communicate with theRAN to modify the bandwidth and/or the QoS of the resource allocation inthe core network that is assigned to the enterprise, NSP, and/or the ASPcomprises: sending a change network resource request message from theenterprise, NSP, and/or the ASP to the RAN that contains a request forchanging the bandwidth and/or traffic priority of the resourceallocation in the core network that is assigned to the enterprise, NSP,and/or the ASP; and sending a change network resource response messagefrom the RAN to the enterprise, NSP, and/or the ASP that contains anacknowledgement for the change network resource request message.
 9. Themethod of claim 1, further comprising: authenticating the enterprise,NSP, and/or the ASP with the RAN prior to using API calls at theenterprise, NSP, and/or the ASP to communicate with the RAN to query theresource allocation and prior to using API calls at the enterprise, NSP,and/or the ASP to communicate with the RAN to modify the bandwidthand/or the QoS of the resource allocation.
 10. The method of claim 9,wherein authenticating the enterprise, NSP, and/or the ASP with the RANcomprises: sending an establish service session request message from theenterprise, NSP, and/or the ASP to the RAN that contains anidentification of the enterprise, NSP, and/or the ASP and authorizationcredentials; and sending an establish service session response messagefrom the RAN to the enterprise, NSP, and/or the ASP that contains anauthentication result.
 11. The method of claim 1, wherein the RAN iscoupled to at least one edge network and wherein using API calls at theenterprise, NSP, and/or the ASP to communicate with the RAN to modifythe bandwidth and/or the QoS of the resource allocation in the corenetwork that is assigned to the enterprise, NSP, and/or the ASPcomprises: using API calls at the enterprise, NSP, and/or the ASP tocommunicate with the RAN to modify the bandwidth and/or the QoS of theresource allocation in the core network and the at least one edgenetwork that is assigned to the enterprise, NSP, and/or the ASP.
 12. Themethod of claim 11, wherein the RAN is coupled to a plurality of edgenetworks of different types and wherein using API calls at theenterprise, NSP, and/or the ASP to communicate with the RAN to modifythe bandwidth and/or the QoS of the resource allocation in the corenetwork and the edge network that is assigned to the enterprise, NSP,and/or the ASP comprises: using API calls at the enterprise, NSP, and/orthe ASP to communicate with the RAN to modify the bandwidth and/or theQoS of the resource allocation in the core network and the plurality ofedge networks that is assigned to the enterprise, NSP, and/or the ASP.13. A Regional/Access Network (RAN) node, comprising: a network resourcemanager module; an Application Programming Interface (API) module thatis configured to facilitate communication between the network resourcemanager module and an enterprise, a Network Service Provider (NSP),and/or an Application Service Provider (ASP); a core network interfacemodule that is configured to facilitate communication between thenetwork resource manager module and a core network; wherein the networkresource manager module is configured to process API calls initiated bythe enterprise, NSP, and/or the ASP to query a resource allocation inthe core network that is assigned to the enterprise, NSP, and/or theASP, and to process API calls initiated by the enterprise, NSP, and/orthe ASP to modify the bandwidth and/or the QoS of the resourceallocation in the core network that is assigned to the enterprise, NSP,and/or the ASP.
 14. The RAN node of claim 13, wherein the core networkinterface module is configured to facilitate communication between thenetwork resource manager module and an Operational Support System (OSS)associated with the core network.
 15. The RAN node of claim 13, furthercomprising: a data repository that is communicatively coupled to thenetwork resource manager module and is configured to store a topology ofcore network resources that are assigned to the enterprise, NSP, and/orthe ASP.
 16. The RAN node of claim 13, wherein the RAN node is aBroadband Remote Access Server (BRAS).
 17. The RAN node of claim 13,wherein the RAN node is a policy enabled router.
 18. The RAN node ofclaim 13, wherein the RAN node is a (multiprotocol label switching) MPLSrouter that supports traffic engineering
 19. The RAN node of claim 13,wherein the core network is coupled to at least one edge network; andwherein the network resource manager module is configured to process APIcalls initiated by the enterprise, NSP, and/or the ASP to query aresource allocation in the core network and the at least one edgenetwork that is assigned to the enterprise, NSP, and/or the ASP, and toprocess API calls initiated by the enterprise, NSP, and/or the ASP tomodify the bandwidth and/or the QoS of the resource allocation in thecore network and the at least one edge network that is assigned to theenterprise, NSP, and/or the ASP.
 20. The RAN node of claim 19, whereinthe core network is coupled to a plurality of edge networks of differenttypes; and wherein the network resource manager module is configured toprocess API calls initiated by the enterprise, NSP, and/or the ASP toquery a resource allocation in the core network and the plurality ofedge networks that is assigned to the enterprise, NSP, and/or the ASP,and to process API calls initiated by the enterprise, NSP, and/or theASP to modify the bandwidth and/or the QoS of the resource allocation inthe core network and the plurality of edge networks that is assigned tothe enterprise, NSP, and/or the ASP.
 21. A system for modifyingbandwidth and/or Quality of Service (QoS) in a Regional/Access Network(RAN) that comprises a core network, the RAN facilitating differentiatedend-to-end data transport between an enterprise, a Network ServiceProvider (NSP), and/or an Application Service Provider (ASP) and acustomer Premises Network (CPN), comprising: means for using ApplicationProgramming Interface (API) calls at the enterprise, NSP, and/or the ASPto communicate with the RAN to query a resource allocation in the corenetwork that is assigned to the enterprise, NSP, and/or the ASP; andmeans for using API calls at the enterprise, NSP, and/or the ASP tocommunicate with the RAN to modify the bandwidth and/or the QoS of theresource allocation in the core network that is assigned to theenterprise, NSP, and/or the ASP.
 22. The system of claim 21, furthercomprising: means for querying the core network directly from the RAN toobtain the resource allocation in the core network that is assigned tothe enterprise, NSP, and/or the ASP.
 23. The system of claim 21, furthercomprising: means for querying an Operational Support System (OSS)associated with the core network to obtain the resource allocation inthe core network that is assigned to the enterprise, NSP, and/or theASP.
 24. The system of claim 21, further comprising: means for modifyingthe bandwidth and/or the QoS of the resource allocation in the corenetwork that is assigned to the enterprise, NSP, and/or the ASP directlyfrom the RAN.
 25. The system of claim 21, further comprising: means forcommunicating with an Operational Support System (OSS) to modify thebandwidth and/or the QoS of the resource allocation in the core networkthat is assigned to the enterprise, NSP, and/or the ASP.
 26. The systemof claim 21, wherein the QoS of the resource allocation in the corenetwork that is assigned to the enterprise, NSP, and/or the ASP istraffic priority.
 27. The system of claim 21 wherein the means for usingAPI calls at the enterprise, NSP, and/or the ASP to communicate with theRAN to query the resource allocation in the core network comprises:means for sending a query network resource request message from theenterprise, NSP, and/or the ASP to the RAN that contains a request forinformation on resource allocation in the core network that is assignedto the enterprise, NSP, and/or the ASP; and means for sending a querynetwork resource response message from the RAN to the enterprise, NSP,and/or the ASP that contains the information on resource allocation inthe core network that is assigned to the enterprise, NSP, and/or theASP.
 28. The system of claim 21, wherein the means for using API callsat the enterprise, NSP, and/or the ASP to communicate with the RAN tomodify the bandwidth and/or the QoS of the resource allocation in thecore network that is assigned to the enterprise, NSP, and/or the ASPcomprises: means for sending a change network resource request messagefrom the enterprise, NSP, and/or the ASP to the RAN that contains arequest for changing the bandwidth and/or traffic priority of theresource allocation in the core network that is assigned to theenterprise, NSP, and/or the ASP; and means for sending a change networkresource response message from the RAN to the enterprise, NSP, and/orthe ASP that contains an acknowledgement for the change network resourcerequest message.
 29. The system of claim 21, further comprising: meansfor authenticating the enterprise, NSP, and/or the ASP with the RANprior to using API calls at the enterprise, NSP, and/or the ASP tocommunicate with the RAN to query the resource allocation and prior tousing API calls at the enterprise, NSP, and/or the ASP to communicatewith the RAN to modify the bandwidth and/or the QoS of the resourceallocation.
 30. The system of claim 29, wherein the means forauthenticating the enterprise, NSP, and/or the ASP with the RANcomprises: means for sending an establish service session requestmessage from the enterprise, NSP, and/or the ASP to the RAN thatcontains an identification of the enterprise, NSP, and/or the ASP andauthorization credentials; and means for sending an establish servicesession response message from the RAN to the enterprise, NSP, and/or theASP that contains an authentication result.
 31. The system of claim 21,wherein the RAN is coupled to at least one edge network and wherein themeans for using API calls at the enterprise, NSP, and/or the ASP tocommunicate with the RAN to modify the bandwidth and/or the QoS of theresource allocation in the core network that is assigned to theenterprise, NSP, and/or the ASP comprises: means for using API calls atthe enterprise, NSP, and/or the ASP to communicate with the RAN tomodify the bandwidth and/or the QoS of the resource allocation in thecore network and the at least one edge network that is assigned to theenterprise, NSP, and/or the ASP.
 32. The system of claim 31, wherein theRAN is coupled to a plurality of edge networks of different types andwherein the means for using API calls at the enterprise, NSP, and/or theASP to communicate with the RAN to modify the bandwidth and/or the QoSof the resource allocation in the core network and the edge network thatis assigned to the enterprise, NSP, and/or the ASP comprises: means forusing API calls at the enterprise, NSP, and/or the ASP to communicatewith the RAN to modify the bandwidth and/or the QoS of the resourceallocation in the core network and the plurality of edge networks thatis assigned to the enterprise, NSP, and/or the ASP.
 33. A computerprogram product for modifying bandwidth and/or Quality of Service (QoS)in a Regional/Access Network (RAN) that comprises a core network, theRAN facilitating differentiated end-to-end data transport between anenterprise, a Network Service Provider (NSP), and/or an ApplicationService Provider (ASP) and a customer Premises Network (CPN),comprising: a computer readable storage medium having computer readableprogram code embodied therein, the computer readable program codecomprising: computer readable program code configured to use ApplicationProgramming Interface (API) calls at the enterprise, NSP, and/or the ASPto communicate with the RAN to query a resource allocation in the corenetwork that is assigned to the enterprise, NSP, and/or the ASP; andcomputer readable program code configured to use API calls at theenterprise, NSP, and/or the ASP to communicate with the RAN to modifythe bandwidth and/or the QoS of the resource allocation in the corenetwork that is assigned to the enterprise, NSP, and/or the ASP.
 34. Thesystem of claim 33, further comprising: computer readable program codeconfigured to query the core network directly from the RAN to obtain theresource allocation in the core network that is assigned to theenterprise, NSP, and/or the ASP.
 35. The computer program product ofclaim 33, further comprising: computer readable program code configuredto query an Operational Support System (OSS) associated with the corenetwork to obtain the resource allocation in the core network that isassigned to the enterprise, NSP, and/or the ASP.
 36. The computerprogram product of claim 33, further comprising: computer readableprogram code configured to modify the bandwidth and/or the QoS of theresource allocation in the core network that is assigned to theenterprise, NSP, and/or the ASP directly from the RAN.
 37. The computerprogram product of claim 33, further comprising: computer readableprogram code configured to communicate with an Operational SupportSystem (OSS) to modify the bandwidth and/or the QoS of the resourceallocation in the core network that is assigned to the enterprise, NSP,and/or the ASP.
 38. The computer program product of claim 33, whereinthe QoS of the resource allocation in the core network that is assignedto the enterprise, NSP, and/or the ASP is traffic priority.
 39. Thecomputer program product of claim 33, wherein the computer readableprogram code configured to use API calls at the enterprise, NSP, and/orthe ASP to communicate with the RAN to query the resource allocation inthe core network comprises: computer readable program code configured tosend a query network resource request message from the enterprise, NSP,and/or the ASP to the RAN that contains a request for information onresource allocation in the core network that is assigned to theenterprise, NSP, and/or the ASP; and computer readable program codeconfigured to send a query network resource response message from theRAN to the enterprise, NSP, and/or the ASP that contains the informationon resource allocation in the core network that is assigned to theenterprise, NSP, and/or the ASP.
 40. The computer program product ofclaim 33, wherein the computer readable program code configured to useAPI calls at the enterprise, NSP, and/or the ASP to communicate with theRAN to modify the bandwidth and/or the QoS of the resource allocation inthe core network that is assigned to the enterprise, NSP, and/or the ASPcomprises: computer readable program code configured to send a changenetwork resource request message from the enterprise, NSP, and/or theASP to the RAN that contains a request for changing the bandwidth and/ortraffic priority of the resource allocation in the core network that isassigned to the enterprise, NSP, and/or the ASP; and computer readableprogram code configured to send a change network resource responsemessage from the RAN to the enterprise, NSP, and/or the ASP thatcontains an acknowledgement for the change network resource requestmessage.
 41. The computer program product of claim 33, furthercomprising: computer readable program code configured to authenticatethe enterprise, NSP, and/or the ASP with the RAN prior to using APIcalls at the enterprise, NSP, and/or the ASP to communicate with the RANto query the resource allocation and prior to using API calls at theenterprise, NSP, and/or the ASP to communicate with the RAN to modifythe bandwidth and/or the QoS of the resource allocation.
 42. Thecomputer program product of claim 41, wherein the computer readableprogram code configured to authenticate the enterprise, NSP, and/or theASP with the RAN comprises: computer readable program code configured tosend an establish service session request message from the enterprise,NSP, and/or the ASP to the RAN that contains an identification of theenterprise, NSP, and/or the ASP and authorization credentials; andcomputer readable program code configured to send an establish servicesession response message from the RAN to the enterprise, NSP, and/or theASP that contains an authentication result.
 43. The computer programproduct of claim 33, wherein the RAN is coupled to at least one edgenetwork and wherein the computer readable program code configured to useAPI calls at the enterprise, NSP, and/or the ASP to communicate with theRAN to modify the bandwidth and/or the QoS of the resource allocation inthe core network that is assigned to the enterprise, NSP, and/or the ASPcomprises: computer readable program code configured to use API calls atthe enterprise, NSP, and/or the ASP to communicate with the RAN tomodify the bandwidth and/or the QoS of the resource allocation in thecore network and the at least one edge network that is assigned to theenterprise, NSP, and/or the ASP.
 44. The computer program product ofclaim 43, wherein the RAN is coupled to a plurality of edge networks ofdifferent types and wherein the computer readable program codeconfigured to use API calls at the enterprise, NSP, and/or the ASP tocommunicate with the RAN to modify the bandwidth and/or the QoS of theresource allocation in the core network and the edge network that isassigned to the enterprise, NSP, and/or the ASP comprises: computerreadable program code configured to use API calls at the enterprise,NSP, and/or the ASP to communicate with the RAN to modify the bandwidthand/or the QoS of the resource allocation in the core network and theplurality of edge networks that is assigned to the enterprise, NSP,and/or the ASP.